| commit | 4a8cad6bfc5d1841e6e59c6a131fa67d7c6e4212 | [log] [tgz] |
|---|---|---|
| author | Ed Merks <ed.merks@gmail.com> | Sun Sep 01 07:15:39 2019 +0200 |
| committer | Ed Merks <ed.merks@gmail.com> | Sun Sep 01 07:15:39 2019 +0200 |
| tree | ecc70ade727c1a49ecb24ae3d854e8c4338231b8 | |
| parent | 03a7a88d6455ebe25a3ce739c21a117b83f9a943 [diff] |
Bug 550628 - Migrate EPP to consistently use EPL 2.0 and SUA 2.0 Change each about.html to the 2.0 version. Change all copyright headers in all file types with references to EPL 2.0, including the copyright property in each feature.properties. Remove all epl-v10.html files and the one EPL-v2.0.html file; the appropriate license file is provided by the license feature resolution during the build. Remove references to the license file from the build.properties of each feature. Change each *.product file to embed a correct version of SUA 2.0 Change-Id: I0c2507d10520a65ff7fc45d8e9ee7aecfcc4ac1b Signed-off-by: Ed Merks <ed.merks@gmail.com>
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/.
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:
archive/ andarchive/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:
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/2019-09/ 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 2019-09 repository:
-Declipse.simultaneous.release.repository="http://download.eclipse.org/releases/2019-09"