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 "Orbit/Easy Bake Builds with Orbit Bundles"
< Orbit
m |
m |
||
| Line 1: | Line 1: | ||
| − | < | + | <h2>AKA Easy Bake Builds with Orbit Bundles</h2> |
During the Eclipse 3.3 M5 cycle, The Eclipse Team (Platform, JDT, PDE and Equinox) started consuming Orbit bundles in their builds. | During the Eclipse 3.3 M5 cycle, The Eclipse Team (Platform, JDT, PDE and Equinox) started consuming Orbit bundles in their builds. | ||
| Line 8: | Line 8: | ||
PDE build also supports checking out multiple versions of the same plugin. | PDE build also supports checking out multiple versions of the same plugin. | ||
| − | + | <br> | |
| − | < | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| + | The process that we use to consume the Orbit builds can be summarized in three simple steps: | ||
| + | <ol> | ||
| + | <li> Use a recent copy of PDE build in your builder with support for fetching prebuilt bundles - for instance 3.3 M6.</li> | ||
| + | <li> <ul> * Consume the Orbit map file directly by fetching it during your build process. The Orbit build process generates map files with the lists of bundles that produced with each build. | ||
| + | For example, see the latest [http://download.eclipse.org/tools/orbit/downloads/drops/S200703161546/ stable Orbit build] - there are links to the map files in | ||
| + | [http://download.eclipse.org/tools/orbit/downloads/drops/S200703161546/directory.txt CVS format] or [http://download.eclipse.org/tools/orbit/downloads/drops/S200703161546/orbitBundles-S200703161546.map http GET] format.</ul> | ||
| + | <p> | ||
OR | OR | ||
| + | </p> | ||
| + | <ul> * Update your local map file entry with the path to the Orbit bundle. The platform releng team has added an orbit.map to their map file project org.eclipse.releng/maps, see example [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/orbit.map?revision=1.12 orbit map] The reason we don't consume the orbit map directly yet is because we are migrating to Orbit bundles on a ongoing basis. If we consumed the Orbit map file directly today, we would have duplicate locations for the several bundles which would cause build issues. Once we have migrated completely to consuming all our third party libraries in Orbit, we plan to modify our build process to consume the Orbit map file directly and remove our orbit.map from our map file project.</ul> | ||
| − | + | <br> | |
<li> If you are adding a new bundle to your build, update the appropriate feature with information for the new Orbit bundle. </li> | <li> If you are adding a new bundle to your build, update the appropriate feature with information for the new Orbit bundle. </li> | ||
| − | </ | + | </ol> |
Each milestone, the Orbit team releases a milestone before the Eclipse team enters milestone week. This allows the Eclipse team to step up to the latest Orbit milestone just in time for milestone week. See the [[Promotion%2C_Release%2C_and_Retention_Policies | Orbit Promotion, Release, and Retention Policies]] for more detail. | Each milestone, the Orbit team releases a milestone before the Eclipse team enters milestone week. This allows the Eclipse team to step up to the latest Orbit milestone just in time for milestone week. See the [[Promotion%2C_Release%2C_and_Retention_Policies | Orbit Promotion, Release, and Retention Policies]] for more detail. | ||
| − | |||
| − | |||
| − | |||
| − | See [[Orbit_Builds | Orbit Builds]] for | + | |
| + | See [[Orbit_Builds | Orbit Builds]] for further information. | ||
Revision as of 10:45, 27 March 2007
AKA Easy Bake Builds with Orbit Bundles
During the Eclipse 3.3 M5 cycle, The Eclipse Team (Platform, JDT, PDE and Equinox) started consuming Orbit bundles in their builds.
To facilitate this transition, PDE build was modified to support fetching builds from a http repository. See Bug 171869 Support for HTTP in map files
PDE build also supports checking out multiple versions of the same plugin.
The process that we use to consume the Orbit builds can be summarized in three simple steps:
- Use a recent copy of PDE build in your builder with support for fetching prebuilt bundles - for instance 3.3 M6.
-
- * Consume the Orbit map file directly by fetching it during your build process. The Orbit build process generates map files with the lists of bundles that produced with each build.
For example, see the latest stable Orbit build - there are links to the map files in
CVS format or http GET format.
OR
- * Update your local map file entry with the path to the Orbit bundle. The platform releng team has added an orbit.map to their map file project org.eclipse.releng/maps, see example orbit map The reason we don't consume the orbit map directly yet is because we are migrating to Orbit bundles on a ongoing basis. If we consumed the Orbit map file directly today, we would have duplicate locations for the several bundles which would cause build issues. Once we have migrated completely to consuming all our third party libraries in Orbit, we plan to modify our build process to consume the Orbit map file directly and remove our orbit.map from our map file project.
- If you are adding a new bundle to your build, update the appropriate feature with information for the new Orbit bundle.
Each milestone, the Orbit team releases a milestone before the Eclipse team enters milestone week. This allows the Eclipse team to step up to the latest Orbit milestone just in time for milestone week. See the Orbit Promotion, Release, and Retention Policies for more detail.
See Orbit Builds for further information.