WTP Build Process and Procedures
This page is to collect general information and references about the WTP build process and procedures. The idea is that any WTP committer can update it, pretty much "on the fly" or "as you go", so that there will often be a bit of a disorganized, stream of consciousness flavor to it, but, occasionally, some kind-hearted committer will stop and organize all the misc. notes and tips and references that are provided into a fun to read treasure.
As of February 1, 2006
Our WTP 1.0.1 contributions are due by EOD on Monday's, we smoke test that build on Tuesday's, and plan to declare it by Wednesday's at noon (eastern time).
Our WTP 1.5 contributions are due by EOD Wednesday's, we smoke test that build on Thursday's, and plan to declare it by Friday's at noon (eastern time).
The platform's releng tool should be used to "release" projects to the map files. Be sure to have the appropriate branch of releng project (which has the map files) loaded in your workspace. R1_0_maintenance for 1.0.x builds, and HEAD for 1.5 builds.
As projects are versioned, please use the "standard" format, in UTC time, following vYYYYMMDD_HHMM. This is important as these cvs tags become the qualifier field of the plugin's version.
Background and Further Reading References
We in WTP following the basic process and recommendations for versioning as the base Eclipse platform. Plugin Versioning
Very helpful guide to builds and automatic testing. Build and Test Automation for plug-ins and features
We base our builds on the Eclipse platform's "basebuilder". Platform-releng
With our WTP specific needs addressed in the WTP project called releng.wtpbuilder. See Media:releng.doc
Our basic server configuration and cruise control triggers is handled by the WTP project called releng.builder (see especially the tools/cruise directory in that project).
And ... never forget Eclipse Help ... search for things related to update manager, PDE, features, site.xml, etc.