WTP Builds This document describes the build policy and how to build WTP components from the command line using Ant scripts. Table
of Contents |
Tools used to manage the build process | ||
1. CVS version 1.10 or higher. For more information on eclipse release engineering tool, refer to the plugin itself. For examples, refer to the org.eclips.releng.eclipsebuilder itself. Readme |
Run the Build | ||||||||||
Run the Build cd to org.eclipse.wtp.releng directory and execute the following command. Alternatively, you can checkout the module org.eclipse.wtp.releng in an eclipse workspace and use the ant run tools. "ant -f cruise.xml" There are three ant targets in cruise.xml (an ant build file): build, publish
[Ant properties to override in buildAll.properties] ". To override a property you must use a syntax like "ant -f cruise.xml -Dclean=true"
|
Ant Properties Settings in buildAll.properties | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following properties are pre-defined in the buildAll.properties file for the build. They can be overridden by setting them at the command line at build time or by changing them directly in the component's build.properties file.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following properties are pre-defined in the build.cfg file for the build. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Build Infrastructure | ||
The automated build process currently runs on a Redhat Linux based build machine hosted at eteration a.s. Build process is run and monitored by cruise control |
How to Create Map File |
A .map file is a java property file which contains mappings of elements to their CVS locations and access methods. Map files are used by PDE Build early in the build process to generate Ant scripts which use the Ant <cvs> task to export source to a directory. This is described further below. |
Map file entries use the following format: |
feature|fragment|plugin@element.Id=<cvs tag>,<access method>:<cvs user>@<cvs repository>,<cvs password>[,<repository path> (no starting slash) ] |
The <repository path> is only required when the module (or directory) containing the source for the element does not match the element.Id or if the directory is not at the root of the repository. |
A map file entry must exist for each feature being built, it's <plugin> elements and it's <includes> elements (ie. nested features and their plug-ins). Adding a plug-in or fragment to a feature therefore requires updating the map files with the new element. |
Map File Entry Examples |
One or more map files can be used to list the elements. The map files can be kept under version control. Some examples of map file projects include org.eclipse.releng, org.eclipse.gef.releng, org.eclipse.ve.releng. |
Generating source features and plug-ins at build time
Source features and plug-ins can be generated at build time by PDE Build. Source features and associated source plug-ins are typically generated for a development kit distributions (i.e. SDK). It is also possible to generate a source plug-in only. This is typically the case for example features or JUnit testing features.
To generate a source plug-in only at build time, you will need to do the following:
|
WTP Release Engineering Team | ||
Ozgur Tumer (ozgur.tumer_at_eteration.com) Dominique Devito (dominique.devito_at_objectweb.org) |