Google Git
Sign in
eclipse / rap / org.eclipse.rap / refs/tags/3.11.0-M1
tag6af68a70f9f68eaadaccf36c7548d799bce19f19
taggerMarkus Knauer <mknauer@eclipsesource.com>Thu Oct 17 10:50:47 2019 +0200
objectedce2a74ca06afcf77a8f845f78d5b7f9c9ad487 
3.11.0-M1
commitedce2a74ca06afcf77a8f845f78d5b7f9c9ad487[log] [tgz]
authorMarkus Knauer <mknauer@eclipsesource.com>Wed Oct 16 14:39:13 2019 +0200
committerMarkus Knauer <mknauer@eclipsesource.com>Thu Oct 17 10:00:32 2019 +0200
treea51409d2200c920b1bb3e109a861e62009be9684
parent669362893f1d5194a9409f81b77e0435324b605b [diff]
Update build configuration for RAP Runtime 3.11.0 M1

- Use Eclipse Platform build S-4.14M1-201910091800
- Use Eclipse Orbit S20191007144714
- Use Eclipse Jetty 9.4.21.v20190926

Disable all cluster tests in SessionFailover and in SessionSerialization
as some tests are failing sporadically, others all the time after the
upgrade of Eclipse Platform and Jetty. At a later time we have to decide
if we invest the time to stabilise the test, or if we completely remove
them.

Also remove org.eclipse.equinox.util from the RAP Basic E4 Equinox
Target feature as it is not shipped by the Eclipse Equinox team any
more, and there are no references in RAP itself. See bug 533801
https://bugs.eclipse.org/bugs/show_bug.cgi?id=533801 for the background
information.

Change-Id: I32fcf6ad0af0d94c9b48f4eb07a03f534623c824
Signed-off-by: Markus Knauer <mknauer@eclipsesource.com>
7 files changed
tree: a51409d2200c920b1bb3e109a861e62009be9684
  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/target/repository/

and a second one with the RAP e4 Runtime bundles in

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