3.0.1-SR1a
Downgrade external bundles in Equinox target feature

The 'RAP Basic Equinox Target' feature in version 3.0.1 (Mars.1)
includes some bundles that caused exceptions and failures. The update to
3.0.2 of the RAP Equinox feature uses the working bundle versions from
the initial Mars release, i.e. downgrades the Equinox, Jetty, and
Eclipse Platform bundles.

Bug 480346 - Provide workaround for multiple NPE in upstream bundles of
RAP 3.0.1 https://bugs.eclipse.org/bugs/show_bug.cgi?id=480346

Change-Id: I11fc4913f1dc51b22d0c4826ecdefa5e30e968aa
Signed-off-by: Markus Knauer <mknauer@eclipsesource.com>
5 files changed
tree: 9a4e48073210c5be644a5e25d89f3ed19938048f
  1. bundles/
  2. examples/
  3. features/
  4. releng/
  5. tests/
  6. .gitignore
  7. CONTRIBUTING.md
  8. Gruntfile.js
  9. package.json
  10. pom.xml
  11. README.md
README.md

Eclipse RAP Runtime (Remote Application Platform)

Thanks for your interest in this project. The [Eclipse RAP Runtime] 1 provides a powerful widget toolkit and integrates well with proven technologies such as OSGi and Java EE. You can write your application entirely in Java, re-use code and benefit from first-class IDE tools.

Git Repository Structure

directorycontent
bundles/all bundle projects
tests/unit test projects
features/feature projects
releng/projects for release engineering
examples/for bundles containing exemplary applications and demo code

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 Runtime

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 Runtime bundles and features in

releng/org.eclipse.rap.build/repository.luna/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!