| commit | e6e1eed64dda20038ec42c7cb9522a3d5593f38c | [log] [tgz] |
|---|---|---|
| author | Markus Knauer <mknauer@eclipsesource.com> | Sat Mar 01 19:17:09 2014 +0100 |
| committer | Markus Knauer <mknauer@eclipsesource.com> | Sat Mar 01 19:17:09 2014 +0100 |
| tree | ecf0be961dfdca7a7fe9ef34c98566f96d7ed0db | |
| parent | 21ea42dac6ce741ec6f9b443ceb75794d43cc9d4 [diff] |
Bug 428744: Adjust EPP to CSS resources move https://bugs.eclipse.org/bugs/show_bug.cgi?id=428744 Update applicationCSSResources property to point to new location in the new bundle org.eclipse.ui.themes in all packages. Change-Id: I6892ae64d688de4a29477c327da45907363cf091
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.