DTP Build Transition
This page describes the changes that will occur when the DTP build transitions from the current system to a PDE based build infrastructure. While the output of both build systems is functionally equivalent, there are some details that will impact both DTP committers and consumers of DTP.
The new DTP build process will use map files. These files specify the features and plug-ins to be included in the build. Further, map files specify a CVS tag for each plug-in and feature. The use of map files is fairly common among Eclipse Foundation projects and brings a number of advantages:
- Committers can use tags to manage which code appears in which build.
- Committers can update the map files to add or remove plug-ins.
- Consumers of DTP interested in duplicating the build process have a specification of exactly what code was used for a given build.
The map files for DTP will be kept in the org.eclipse.datatools.releng CVS module, to which all DTP committers have write access.
Naturally, with power comes responsibility. Aside from the obvious requirement to keep the map files and CVS tags current, committers should be very care when adding or removing plug-ins, since doing so can introduce dependencies and build breakage. Therefore, aside from update the existing tags used in the map files, we encourage committers to file bugs with proposed changes (additions/removals/etc.) for review by the release engineering team and PMC before making such changes.
Use of ".qualifier"
As described in the DTP Plug-in Versioning Policy, "A DTP plug-in version number has four fields, separated by a ".": Major.Minor.Service.Qualifier"
Previously DTP committers where required to update the qualifier field with each plug-in change. Starting with the new build system, the time stamps in all DTP 1.6 plug-ins will be changed to ".qualifier" and the DTP build process will control update of these values. Thus, no further action in this area is required by DTP plug-in owners.
The ".qualifier" field will be set to a current time stamp with each DTP build.
Format of Distribution Version Stamp
Currently DTP distributions (end user and extender zips) have the following format:
with the exact time stamp varying according to the build date. In the new build system, the format will be like:
again, with the exact time stamp varying according to the build date. Consumers relying on a specific format (say for automatic consumption in a build process) might need to update their matching patterns for this change.
Note: Using Shanghai time.
Nightly builds take place from Monday to Thursday. Integration builds takes place on Friday.