3.8.0-RC1
Update build configuration for RAP Tools 3.8.0 RC1

- Use Eclipse Platform build S-4.11RC1-201903010040

Change-Id: I8ec21525cf0581f16ac82c6255dbe4d8c7f9c5c2
Signed-off-by: Markus Knauer <mknauer@eclipsesource.com>
2 files changed
tree: 7aa12b24f6f51688cad8a391f48eddb627f044f8
  1. bundles/
  2. features/
  3. releng/
  4. tests/
  5. .gitignore
  6. CONTRIBUTING.md
  7. pom.xml
  8. README.md
README.md

Eclipse RAP Tools (Remote Application Platform)

Thanks for your interest in this project. The [Eclipse RAP Tools] 1 provides additional tooling that can be installed into Eclipse in order to simplify working with the RAP Runtime.

Git Repository Structure

directorycontent
bundles/all bundle projects
tests/unit test projects
features/feature projects
releng/projects for release engineering

Additional information regarding source code management, builds, coding standards, and more can be found on the [Getting involved with RAP development] 2 pages. For more information, refer to the [RAP wiki pages] 3.

Building RAP Tools

The RAP project uses Tycho with Maven to build its bundles, features, examples, and p2 repositories, and it's easy to run the build locally! All you need is Maven installed on your computer, and then you need to run the following command from the root of the Git repository:

mvn clean verify

As a result, you'll get a p2 repository with all the RAP Tools bundles and features in

releng/org.eclipse.rap.tools.build/repository/target/repository/

Official builds are available from the [RAP Download page] 4.

Contributions

Before your contribution can be accepted by the project, you need to create and electronically sign the [Eclipse Foundation Contributor License Agreement (CLA)] 5 and sign off on the Eclipse Foundation Certificate of Origin.

For more information, please visit [Contributing via Git] 6.

License

[Eclipse Public License (EPL) v1.0] 7

Contact

Contact the project developers via the [RAP Forum] 8 or the project's [“dev” mailing list] 9.

Search for bugs

This project uses Bugzilla to track [ongoing development and issues] 10.

Create a new bug

Be sure to [search for existing bugs] 10 before you [create a new RAP bug report] 11. Remember that contributions are always welcome!