Difference between revisions of "DTP Build Transition"

From Eclipsepedia

Jump to: navigation, search
Line 4: Line 4:
 
==Changes==
 
==Changes==
 
===Map Files===
 
===Map Files===
 
+
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.
 +
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"===
 
===Use of ".qualifier"===
  

Revision as of 16:47, 27 February 2008

Back to DTP Release Engineering

Contents

Introduction

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.

Changes

Map Files

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.

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"

Format of Version Stamp

Build Schedule

Contact the Build Team