Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Data Tools Platform:Release Engineering

Revision as of 23:10, 26 August 2007 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Back to DTP Main Page

This information is preliminary. While this system is available within CVS, it is not currently used to generate the DTP builds.

This page details the build system utilised by DTP.


This system was derived from the system used by WTP and STP (and probably others). The system performs the following tasks:

  • Component builds
    • builds plugins and features
    • generates install ZIP
    • generates update site JARs
  • Component testing
    • executes unit tests
    • generates results files
  • Update site generation
  • Download site generation
    • generates html for download site
    • incorporates build settings
    • incorporates build results (e.g. warnings/errors)
    • incorporates test results
  • Uploading build information
    • publishes generated files to DTP web site


The build system is designed to organized as follows:

a group of one or more components
synonymous with feature; the input to the builder/assembler/packager

The system is comprised of custom Ant scripts which are used to initialize build properties, download dependencies, invoke the PDE builder for individual components, generate site files.

The head-less PDE builder is used to generate plugin JARs and ZIPs. The PDE builder executes a build using information in the feature and plugin manifests. This helps ensure the plugin build environment is similar to its execution environment.

The system is composed of two projects within CVS:


This project contains the following files:

*.map files
used by the PDE builder to locate and fetch source for the build. These files are used to specify the following information:
  • plugin/fragment/bundle/feature ID
  • plugin/fragment/bundle/feature location in CVS (project and path)
  • tag to fetch
specifies names and download locations for dependencies (e.g. Eclipse platform, EMF, GEF)
specifies which tag of the org.eclipse.datatools.releng.builder should be used to execute the build


This project contains the scripts used to execute the build. It is divided into the following sections (by folder):

  • components
  • cruise
  • distribution
  • scripts

At the root is the build.xml file that drives the build for a particular distribution (i.e. the distribution must be specified when this file is invoked; e.g. dtp).

components folder

The components folder contains a folder for each component that will be built. These folders may be used directly with PDE builder as the buildLocation for the build.

A component is synonymous with a feature. The feature specified by the component is used to drive the build. See the PDE builder documentation for more information.

This system deviates from the general PDE build integration by the following:

  • allElements.xml is incorporated directly within customTargets.xml
    The allElements and[.config.spec] targets are defined directly within customTargets.xml.
  • most of the targets for customTargets.xml are imported from scripts/build/defaultCustomTargets.xml
    scripts/build/defaultCustomTargets.xml contains targets that are common to all component builds (e.g. fetching dependencies). (Note, individual components may override any targets imported from defaultCustomTargets.xml.)
  • dependency.xml
    This file is used to specify the dependencies required by the component. The file in org.eclipse.datatools.releng must contain an entry for each of the group IDs specified in this file.

cruise folder

The cruise folder contains scripts for driving the main build from CruiseControl. The build.xml file within this folder fetches the org.eclipse.datatools.releng and org.eclipse.datatools.releng.builder projects, then invokes the main build file in the root of org.eclipse.datatools.releng.builder.

TODO: Some files in this folder need to be updated for use with DTP; specifically the following files:

  • config.xml

distribution folder

Contains distribution specific build files. Each folder in this directory uses the following naming convention:

<distribution name>.<target name>
e.g.,, etc.

The scripts within these folders are pretty specialized (although there may be an opportunity to refactor some of these scripts so common targets can be shared across distributions).

The breakdown of target types is as follows:

invokes the PDE builder for each component in the distribution.
generates the download site files for the build. (verify: does this also generate the update site)
TODO: document this
invokes tests and consolidates results
uploads generated build zips and site files to the web site
TODO: document this

The following distributions and targets are defined for DTP:

the main DTP distribution
builds component zips
builds download site files (TODO: should update the html template files to fit in with the new-look Eclipse web site)
TODO: needs to be updated for DTP
TODO: needs to be updated for DTP

scripts folder

Contains common scripts available for use from distribution and component build scripts. For example, scripts/dependency contains scripts for downloading dependencies required by a particular component; scripts/build/build.xml contains targets for executing the PDE builder for a particular component.

Still to Do

  1. Update ODA plugins for use with PDE builder
    The ODA plugins are currently built using custom build scripts. Need to make sure the resources used by the PDE builder are consistent with the custom scripts.
  2. Integrate generation of ISV documentation
  3. Add documentation plugins (user and ISV) to respective featurs
  4. Integrate unit tests
  5. Fix upload target (verify/update settings in
  6. Ensure all relevant properties are passed to the PDE builder
    The PDE builder is invoked through a Java task, meaning properties are not inherited. Need to make sure any PDE builder specific properties are passed through as vmargs.
  7. Notify tasks in scripts/monitoring need to be updated
  8. Update html templates so they are compatible with Phoenix.

DTP Component Breakdown

Note, this is preliminary and does not reflect the current Europa release strategy.

The following components are defined:

core connectivity plugins: connection profile framework, driver definition framework, data source explorer view
provides JDT classpath container extension for driver definitions
base ODA framework
SQL development tools framework
vendor specific plugins for use with sqldevtools
specialized plugins for use with connectivity-oda
all DTP plugins, with the exception of source and ISV documentation
all DTP plugins including source and ISV documentation

Executing a Build

Building a Distribution

A distribution build may be exectuted through either of the following build files: (note, these may be invoked using a normal Ant install; i.e. no special tasks or additional libraries are required)

  • org.eclipse.datatools.releng.builder/cruise/build.xml
    This is the build file used with CruiseControl. Executing the build through this file will fetch the org.eclipse.datatools.releng and org.eclipse.datatools.releng.builder projects, the former will be fetched using the tag specified by the mapVersionTag property, while the latter will be fetched using the tag specified by the dtpBuilderVersion property located in the fetched org.eclipse.datatools.releng/maps/build.cfg file. The build is then executed through the fetched org.eclipse.datatools.releng.builder/build.xml file.
  • org.eclipse.datatools.releng.builder/build.xml
    This is the main build file for the DTP, containing targets for building a distribution's build, site, api, tests, upload and whatisfixed targets. There is no default target for this build file, so you must specify one or more on the command line.

The following properties must be defined when invoking either of the above targets:

The architecture (e.g. x86)
The operating system (e.g. win32)
The windowing system (e.g. win32)
The working directory for the build (e.g. c:\tmp\dtp\build)
The build classpath for plugins built against J2SE-1.4 execution environment. Currently, this must include rt.jar, jsse.jar and jce.jar (e.g. c:\j2sdk1.4.2\jre\lib\rt.jar;c:\j2sdk1.4.2\jre\lib\jsse.jar;c:\j2sdk1.4.2\jre\lib\jce.jar)
Similar to J2SE15, but applies to J2SE-1.5 execution environment.
Location of lpgjavaruntime.jar file. This is required for building SQL tools. This file is copied into org.eclipse.datatools.lpg/lib prior to building and deleted prior to packaging.
Set to true when testing the build system.
Set to true to remove any existing build directory (only for cruise/build.xml)

Building a Component


Back to the top