Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox/p2/Getting Started for Releng"
(New page: The Eclipse Ganymede (3.4) release introduces Equinox_p2, a new platform for installing, managing, and updating Eclipse-based applications and extensions. p2 offers significantly impro...) |
|||
| Line 1: | Line 1: | ||
The Eclipse Ganymede (3.4) release introduces [[Equinox_p2]], a new platform for installing, managing, and updating Eclipse-based applications and extensions. p2 offers significantly improved functionality over the platform Update Manager used in previous releases. Leveraging this new functionality requires some changes for people building and assembling Eclipse-based applications and add-ons. This article helps buildmeisters and release engineers to get started with adopting p2. See also [[Equinox p2 Getting Started]] for an introduction to p2 from an end-user perspective. | The Eclipse Ganymede (3.4) release introduces [[Equinox_p2]], a new platform for installing, managing, and updating Eclipse-based applications and extensions. p2 offers significantly improved functionality over the platform Update Manager used in previous releases. Leveraging this new functionality requires some changes for people building and assembling Eclipse-based applications and add-ons. This article helps buildmeisters and release engineers to get started with adopting p2. See also [[Equinox p2 Getting Started]] for an introduction to p2 from an end-user perspective. | ||
| + | == What do I do if I produce zips of plug-ins and features? == | ||
| + | |||
| + | If your project produces zips of plug-ins and features for consumption by others, no action is required. p2 provides a number of ways for an end-user to install such zips: | ||
| + | |||
| + | * Drag into the "Software Updates" dialog in the UI | ||
| + | * Unzip into the eclipse/dropins folder | ||
| + | * Unzip directly on eclipse root directory (generally not recommended as it makes it difficult to distinguish added content from the base application). | ||
| + | |||
| + | However, when p2 encounters raw plug-ins and features, it needs to do some processing on the content to compute p2 metadata. This results in a slower experience for the end user when the content is first installed. You can optimize this by creating a p2 repository that contains your plugins and features. A p2 repository is created automatically if you export plug-ins and features from your IDE using the PDE plug-in export wizard. This adds a ''content.xml'' and ''artifacts.xml''. p2 also provides a ''p2.generator'' Ant task or stand-alone application that can be invoked programmatically or from a build script to produce a p2 repository. See [[Equinox p2 Metadata Generator]] for more information about this generator application. | ||
[[Category:Equinox p2|Releng]] | [[Category:Equinox p2|Releng]] | ||
Revision as of 17:35, 29 March 2008
The Eclipse Ganymede (3.4) release introduces Equinox_p2, a new platform for installing, managing, and updating Eclipse-based applications and extensions. p2 offers significantly improved functionality over the platform Update Manager used in previous releases. Leveraging this new functionality requires some changes for people building and assembling Eclipse-based applications and add-ons. This article helps buildmeisters and release engineers to get started with adopting p2. See also Equinox p2 Getting Started for an introduction to p2 from an end-user perspective.
What do I do if I produce zips of plug-ins and features?
If your project produces zips of plug-ins and features for consumption by others, no action is required. p2 provides a number of ways for an end-user to install such zips:
- Drag into the "Software Updates" dialog in the UI
- Unzip into the eclipse/dropins folder
- Unzip directly on eclipse root directory (generally not recommended as it makes it difficult to distinguish added content from the base application).
However, when p2 encounters raw plug-ins and features, it needs to do some processing on the content to compute p2 metadata. This results in a slower experience for the end user when the content is first installed. You can optimize this by creating a p2 repository that contains your plugins and features. A p2 repository is created automatically if you export plug-ins and features from your IDE using the PDE plug-in export wizard. This adds a content.xml and artifacts.xml. p2 also provides a p2.generator Ant task or stand-alone application that can be invoked programmatically or from a build script to produce a p2 repository. See Equinox p2 Metadata Generator for more information about this generator application.