I think there is a bit of confusion.
My understanding from the workshop was that the versioning tools
we discussed verify that a current build adheres to the versioning numbering
but do not perform the automatic versioning
of a build.
There are two separate issues issues
with versioning in a build
1) Cvs tagging of projects to be included
in a build - Currrently for the platform team, this is performed by the
developers themselves using the releng tool (See http://download.eclipse.org/eclipse/downloads/drops/S-3.3M2-200609220010/winPlatform.php#org.eclipse.releng).
Developers on our team specify the cvs tag of a project that they
want to submit to an integration build by using the releng tool to update
the cvs tag of their project in the org.eclipse.releng project in
/cvsroot/eclipse. See http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/
These cvs tags in turn are used to generate
the qualifiers for the plugin and feature by PDE Build. See http://wiki.eclipse.org/index.php/Version_Numbering#When_to_change_the_qualifier_segment
This approach ensures that new jars
are only copied to an update site when there is actually new content, not
with every integration build.
Our build process rtags the map file
project with the buildId to capture what was submitted to a build.
For example, see http://download.eclipse.org/eclipse/downloads/drops/S-3.3M2-200609220010/directory.txt
Other teams may have other approaches
to this issue depending on their build environment.
2) Ensuring the qualifiers generated
from cvs tags by PDE build adhere to the versioning standard. Since the
cvs tags are submitted by humans, they are subject to error :-) We
have a tool that a verifies that they are correct compared to an older
build and adhere to the versioning guidelines. This will run as a
JUnit test in our build.
I apologize that this is not available
was not in accordance with the date agreed to at the workshop. I underestimated
the amount of work involved with the M2 and 3.2.1 release. I hope
to have this released to our build within the next two weeks.
Thomas Hallgren <thomas@xxxxxxx> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
10/01/2006 07:19 AM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
tools for download and evaluation (Eclipse
During the Europa Build Workshop we discussed making common build-tools
available for download and evaluation. One of the more important ones
was a tool that would help with automatic versioning of a build (see:
Buckminster currently lacks such a tool. The general opinion was that
there was at least four of them in existence and I don't want to invent
a fifth :-)
What is the status of this action item?
cross-project-issues-dev mailing list