After we declared R2.0 "real" we actually did version the plugins in the repository with the tag R2_0. Until then there was no R2_0 tag.
The source build scripts where generated at build time. So the fetch scripts you have are the same ones that built GM6 before it was promoted to R2.0.
So we could go and regenerate source build zips that contained the R2_0 tag for all the plugins. However, each plugin would still have to appear in the fetch scripts since, unfortunately, not all the CVS projects are part of the R2_0 build. I'm not sure how I feel about this. As it stands currently, I know the fetch scripts you are running are the ones used to generate the build. If I change them, that will not be precisely true. Granted the change is trivial but it seems the trivial changes are always the ones that smoke you.
In the past (and currently) we have a build strategy that gives control over the tags to the plugin owners. The plugin owners then "release" the desired versions of their plugins to the map files in org.eclipse.releng. I don't think we want to change this *but* it might be a good idea if each Integration build was tagged by the builder, at build time with the build name (I20020714). This could be the best of both worlds. It allows plugin owners to have "total" control over the tag names and what is released to the build, but also provides the ability of easily loading plugin versions matching a particular build after the build has happened.
What do people think about this?
Andrew Haley <aph@xxxxxxxxxxxxxxxxxxxx>
07/18/2002 10:16 AM
To: "Dean Roberts" <Dean_Roberts@xxxxxxx>
Subject: [eclipse-dev] Source builds available
Dean Roberts writes:
> Hi folks,
> At last, a flavour of source builds are now available for Eclipse.
> Since we Eclipse uses a part of Eclipse (PDE) to generate the build
> scripts what we have for you right now are sets of pre-generated
> build.xmls and fetch scripts that can fetch and build a particular version
> of Eclipse. This allows you to build Eclipse with only Ant, CVS and a JDK
> We are working on a couple of other source build scenarios.
> 1) A build with pregenerated build.xml files but a zip file that
> contains all the source files so that you don't have to do the cvs fetch.
> This should be up in a couple of days.
> 2) A source build that contains a .jar with the pde and a few
> other essential plugins. While this does not satisfy the "build from
> scratch" requirement, it doe satisfy the "build Eclipse the same way
> Eclipse.org builds Eclipse" requirement. This one may take a couple more
> weeks to put up.
> So for now, you can check out the fetch and build for the 2.0 eclipse.
> Source builds will also be part of each every new Nightly and Integration
> build. Please take a look and let us know what you think.
I'm using eclipse-sourceBuild-srcFetch-2.0.zip.
There seems to be a bewildering variety of tags used for the various
components; I've attached a list to the end of this mail.
What is the reason for this? Is there any reason not to tag the whole
source tree with "Eclipse-2.0-release" and then check out everything
against the same tag?