Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Equinox p2 - Building"

Line 45: Line 45:
 
* should enhance so instead of building several different things, we should build one big feature and then use the packager to put together the things that we need
 
* should enhance so instead of building several different things, we should build one big feature and then use the packager to put together the things that we need
  
[[Category:Equinox|Provisioning - Building]]
+
[[Category:Equinox p2|Building]]
[[Category:Provisioning]]
+

Revision as of 15:33, 1 October 2007

This page contains information on how to build the Equinox p2 code.

Workspace Setup

A project has been created in CVS which contains a builder and the build scripts for the new provisioning work. Check out the project from CVS with the following information:

server: dev.eclipse.org
repository: /cvsroot/eclipse
project: /equinox-incubator/provisioning/org.eclipse.equinox.prov.releng.builder

There is a builder sub-directory which contains an Eclipse install with the minimal bundles required to run the build. It is a Window build and should be replaced with a Linux drop if that is appropriate for the machine that you are running on.

Open the run.xml file for editing. There are a few properties in here that you will have to modify.

<property name="prov.root" value="c:" />
<property name="prov.output.base" value="${prov.root}/equinox.prov.build" />
<property name="prov.install.folder" value="equinox.prov" />
<property name="sdk.archive" value="${prov.root}/downloads/eclipse-SDK-3.4M1-win32.zip" />
<property name="rcp.delta.archive" value="${prov.root}/downloads/eclipse-RCP-3.4M1-delta-pack.zip" />
<property name="rcp.archive" value="${prov.root}/downloads/eclipse-RCP-3.4M1-win32.zip" />
<property name="prov.java" value="d:/java/jdk1.5.0_11/jre/bin/java" />

Then from the command-line, run the appropriate build file: either build_win.bat or build_lnx.

Note: you must have the CVS executable available from the command-line in order for the checkout to work.

Output

  • The Agent zip will be in ${prov.output.base}/equinox-prov-agent-<timestamp>-win32.zip
  • The Metadata and Artifact repositories will be in ${prov.output.base}/servers

What Happens

  1. build features for the director, metadata generator, and self-hosting bundles
  2. build the agent from a product
  3. generate the metadata for the agent
  4. run the director and install the agent from the generated metadata and artifacts
  5. zip up the agent install
  6. generate the metadata for the self-hosting bundles and Eclipse SDK

TODO

  • integrate with the regular Platform builds
  • write code to determine the output file of the build
  • should enhance so instead of building several different things, we should build one big feature and then use the packager to put together the things that we need

Back to the top