The Eclipse Packaging Project (EPP) provides the download packages based on the content of the yearly Simultaneous Release. The download packages are provided from www.eclipse.org/downloads/.
It's easy to run the build locally! All you need is Maven and then you need to tell Maven which package(s) to build via profile. As an example, the following command from the root of the Git repository builds the RCP/RAP package against the Simultaneous Release staging p2 repository:
mvn clean verify -Pepp.package.rcp
This build creates output in two places:
- tar.gz/zip archives with the packages in
archive/and - a p2 repository with the EPP artifacts in
archive/repository/.
If you are running the build on Windows, the last build step will currently fail.
This failure can be circumvented by skipping the last step which aggregates the
filtered EPP artifacts from the packages into a new p2 repository. For further
details see bug 426416.
At the moment it is advised to run the build command on Windows with package
only:
mvn clean package -Pepp.package.rcp
In addition to that it is not possible to create zip and tar.gz archives on
Windows due to missing Bash scripting capabilities. On Windows, the output of the
build is the eclipse directory that contains the usual content from the zip
archive. This directory can be found below (e.g. RCP package)
packages/org.eclipse.epp.package.rcp.product/target/products/.
Each package uses its own profile:
- epp.package.automotive
- epp.package.cpp
- epp.package.dsl
- epp.package.java
- epp.package.jee
- epp.package.modeling
- epp.package.parallel
- epp.package.php
- epp.package.rcp
- epp.package.reporting
- epp.package.scout
- epp.package.standard
- epp.package.testing
With the signing profile enabled, the build artifacts (bundles, features) and the Windows and Mac OSX executables are signed. This is done by using the Eclipse Foundation internal signing service and can be activated only if the build is running there.
- eclipse-sign