Skip to main content
Jump to: navigation, search

Difference between revisions of "EPP/Galileo Packages"

< EPP
(Package Definition)
Line 18: Line 18:
 
==Package Definition==
 
==Package Definition==
  
 +
All EPP consists of two projects that are available from the EPP CVS. Changes should be requested by submitting a bug in bugzilla with an attached patch.
 +
 +
<code><pre>
 +
cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/technology checkout -P org.eclipse.epp/packages
 +
</pre></code>
 +
 +
===org.eclipse.epp.package.PACKAGENAME.feature===
 +
 +
* eclipse_PACKAGENAME_galileo.xml: This file is the old EPP configuration file. It is only used to drive the website and contains the name, description, links to bugzilla, name of the maintainer, links to new and noteworthy, etc. The content of the package is not defined in this file (see feature.xml)!
 +
* epp.product: Product configuration file that is used to generate the p2 repository which can be used by the p2 director to build the final package.
 +
* feature.xml: See the examples in CVS. This file contains the branding plug-in and defines the content of the package [currently] in the "requires" section of the feature definition, e.g.
 +
 +
<code><pre>
 +
  <requires>
 +
      <import feature="org.eclipse.cvs" version="1.1.0" match="greaterOrEqual"/>
 +
      <import feature="org.eclipse.equinox.p2.user.ui" version="1.1.0" match="greaterOrEqual"/>
 +
      <import feature="org.eclipse.help" version="1.1.0" match="greaterOrEqual"/>
 +
      ...
 +
</pre></code>
 +
 +
===org.eclipse.epp.package.PACKAGENAME===
  
 
==Local Package Build==
 
==Local Package Build==

Revision as of 10:41, 6 May 2009

Overview

  • All EPP Packages for the Galileo release are build from p2 repositories with the p2 director.
  • Every package is defined by
    • a feature
    • a branding plug-in
    • a epp.product file that is used to generate the EPP p2 repository
    • a eclipse_PACKAGENAME_galileo.xml file (the old EPP config file) that is used for generating the website only.
  • [currently] EPP p2 repository: http://download.eclipse.org/technology/epp/packages/galileo/milestones/

p2 Repositories

EPP uses the following p2 repositories:

Package Definition

All EPP consists of two projects that are available from the EPP CVS. Changes should be requested by submitting a bug in bugzilla with an attached patch.

cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/technology checkout -P org.eclipse.epp/packages

org.eclipse.epp.package.PACKAGENAME.feature

  • eclipse_PACKAGENAME_galileo.xml: This file is the old EPP configuration file. It is only used to drive the website and contains the name, description, links to bugzilla, name of the maintainer, links to new and noteworthy, etc. The content of the package is not defined in this file (see feature.xml)!
  • epp.product: Product configuration file that is used to generate the p2 repository which can be used by the p2 director to build the final package.
  • feature.xml: See the examples in CVS. This file contains the branding plug-in and defines the content of the package [currently] in the "requires" section of the feature definition, e.g.
   <requires>
      <import feature="org.eclipse.cvs" version="1.1.0" match="greaterOrEqual"/>
      <import feature="org.eclipse.equinox.p2.user.ui" version="1.1.0" match="greaterOrEqual"/>
      <import feature="org.eclipse.help" version="1.1.0" match="greaterOrEqual"/>
      ...

org.eclipse.epp.package.PACKAGENAME

Local Package Build

A local package build is the same as running the p2 director on the above p2 repositories and installing special root IU's from the repositories. Available root IU's: epp.package.cpp, epp.package.java, epp.package.jee, epp.package.modeling, epp.package.php, epp.package.pulsar, epp.package.rcp, epp.package.reporting.

Using the eclipse.org repositories

Using a local repository generated from the .product file

Back to the top