| commit | 782863e6249a851a82f01ac8d5ef562e7ddf729a | [log] [tgz] |
|---|---|---|
| author | Ivan Furnadjiev <ivan@eclipsesource.com> | Thu Jun 27 13:01:29 2019 +0300 |
| committer | Markus Knauer <mknauer@eclipsesource.com> | Thu Jun 27 13:12:04 2019 +0200 |
| tree | 4321cc5683257749995cd3436aa0ab7ca78616a1 | |
| parent | 24fb7742323bef8a2d1fa2662e427182e573680d [diff] |
Change Java Execution Env of all RAP bundles to 1.8 Eclipse platform switched their BREE to 1.8 to almost all bundles. There is no point to stay on a lower version. Change-Id: I936d19b73042de765564df1ee8aee0e34880e25b
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.
| directory | content |
|---|---|
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.
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.
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.
[Eclipse Public License (EPL) v1.0] 7
Contact the project developers via the [RAP Forum] 8 or the project's [“dev” mailing list] 9.
This project uses Bugzilla to track [ongoing development and issues] 10.
Be sure to [search for existing bugs] 10 before you [create a new RAP bug report] 11. Remember that contributions are always welcome!