|tagger||Jonah Graham <email@example.com>||Tue Dec 07 10:59:01 2021 -0500|
|author||Jonah Graham <firstname.lastname@example.org>||Thu Dec 02 12:00:00 2021 +0000|
|committer||Jonah Graham <email@example.com>||Thu Dec 02 12:00:00 2021 +0000|
Set version qualifiers with setGitDate script Change-Id: Iba86a915323b9cd66de9d5650c0a1a23f967195e
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/eclipse-packages/.
Please see RELEASING.md in this repo for instructions on the release process for the EPP project.
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:
In the past the last step in the build process used to fail. For further details see bug 426416. If that happens again
mvn clean package -P"epp.package.rcp"
Each package uses its own profile:
macOS dmg files can only be created within the Eclipse Foundation network. To enable creating dmg files enable the eclipse-package-dmg profile. Without eclipse-package-dmg enabled, the .tar.gz for macOS will be created regardless.
With the signing profiles enabled, the build artifacts (bundles, features) and the Windows and macOS 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.
By default, the EPP build uses the content of the Eclipse Simultaneous Release Staging repository at http://download.eclipse.org/staging/2020-03/ as input. Sometimes it is desired to build against another release (e.g. a different milestone), or against a local mirror of this repository. This can be achieved by setting the Java property
eclipse.simultaneous.release.repositoryto another URL. As an example, by adding the following argument to the Maven command line, the EPP build will read its input from the composite Eclipse 2020-03 repository: