| commit | 7069485ab219ab2988c4066ac21405acde9ba441 | [log] [tgz] |
|---|---|---|
| author | Markus Knauer <mknauer@eclipsesource.com> | Sat Mar 01 18:30:39 2014 +0100 |
| committer | Markus Knauer <mknauer@eclipsesource.com> | Sat Mar 01 18:30:39 2014 +0100 |
| tree | 93fb2c2f4c209061f10c81f7a666807c3dde78d0 | |
| parent | c36aa52084233ecf85762d36b93ae82922eca872 [diff] |
Update packages with new Eclipse Foundation logo This update includes the 16/32/48/258 pixel png images and the about gif image. It updates all packages except the ones that had their own images in the past (in particular the Java EE package). Change-Id: I591cad90da0ccf985298a85a70dfa0b7e6103c6d
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:
packages/org.eclipse.epp.package.rcp.product/target/products/ andrepository/.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
Each package uses its own profile:
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.