[epp-dev] repository discussion - epp+galileo or galileo-only

[Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx>]

Hi Thomas,

here is some input - let me know if you need more information about the process:

First step: Build a p2 repository that can be used by the p2 director to build a package.
Second step: Run the p2 director for each of the 4 platforms, create the package, zip it into an archive, etc.

While the second step is already scripted, the first one needs automation and is currently done by exporting things from my own workspace.

In order to customize the packages, each package has two projects in the EPP CVS (dev.eclipse.org:/cvsroot/technology - org.eclipse.epp/packages/...).

[1] A feature project that 'includes' the org.eclipse.platform feature and lists the package content as 'required' features.
[2] A branding plug-in with
  - the epp.product file used for the build, contains the product definition, which application to run, JVM settings, eclipse.ini information, etc.

  - the eclipse_XYZ_350.xml file (the former EPP config file) with the meta-information for the website
  - the package-specific plugin_customization.ini with the default perspective and probably other information

The manually created 'output' p2 repository for all packages is here http://download.eclipse.org/technology/epp/packages/galileo/milestones/ and contains ./plugins/..., ./features/... and of course the platform specific binaries in ./binaries/...

This p2 repository is used together with the main Galileo p2 repository to create the packages.

Regards, Markus