From: Markus B. <Mar...@gm...> - 2006-02-05 18:27:56
|
Hi all! Since there were problems with the nightly builds after changes to the plug-in versions, I've simplified the versioning in the following way. I assumed the following prerequisites: * builds are done seldom from the workspace, i.e. the developer usually develops with a runtim workspace (Run-> Eclipse Application) and does not build the plugin as zip file from the feature.xml * all sorts of builds (nightly, integration, rc, release) are performed on the cruise control host or elsewhere with the headless build scripts * the org.rubypeople.* plug-ins are so tightly coupled that independent versioning doesn't make sense With these prerequisites the following schema seems to be most appropriate * All plug-ins get the version 0.0.0 with the exception of org.kxml and org.epic.regexp. * In the feature.xml file the version of the feature itself and the org.rubypeople.* plug-in get the version 0.0.0, too. If you want to build from the workspace, there are now 2 steps necessary: 1. open feature.xml and replace all 0.0.0 entries (for the feature and all included plug-ins) with the version you want to build 2. call export and the build automatically adapts the versions of the plug-ins to the versions given in the feature.xml file The automatic build on the cruise control server replaces all versions (i.e. 0.0.0) with the appropriate version. In addition to the RDT feature itself also the test feature with the unit and integration tests must be considered here. Using the 0.0.0 schema there will be no need to change the plug-in or feature versions at all: the release and integration builds on the cruise control server use the same build scripts as the nightly build and therefore there is no need for a manual setting of versions. After a release a new nightly build prefix (e.g. 0.8.0 instead of 0.7.0) can be set in cruise control's config.xml file. Please also note that changing feature.xml with the wizard is dangerous, because in that case comments are removed. And currently we use one comment which the automatic build needs in order to produce the source feature. Thanks Markus |