I think it’s because
BIRT don’t have the kind of integration build. We choose one nightly
build to be voted for milestone build.
I didn’t find a
better way to do versioning control. So I check out from HEAD version and make
out the version for each plugin. BIRT version tool doesn’t perform
tagging action. It just generates the plugin version according to CVS diff log
and replace the qualifiers in MANIFEST.MF.
-Xiaoying
From:
pde-build-dev-bounces@xxxxxxxxxxx [mailto:pde-build-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Tuesday, October 24, 2006
8:33 AM
To: Eclipse PDE Build developers
list.
Subject: Re: [pde-build-dev] Re:
Fw: questions about the BIRT build system
Curious. Why don't developers do the
tagging? Presumably developers have to decide what is good and what is
not. It should also be developers who are deciding what goes into an
integration build. So it is unclear how the BIRT version tool can do
these things for you.
Jeff
Andrew
Niefer/Ottawa/IBM@IBMCA
Sent by: pde-build-dev-bounces@xxxxxxxxxxx
10/23/2006 02:32 PM
Please
respond to
"Eclipse PDE Build developers list."
<pde-build-dev@xxxxxxxxxxx>
|
|
To
|
"Sue Lee" <slee@xxxxxxxxxxx>,
"Xiaoying Gu" <xgu@xxxxxxxxxxx>, "Eclipse PDE Build
developers list." <pde-build-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
[pde-build-dev] Re: Fw:
questions about the BIRT build system
|
|
The map files are concatentated together into the directory.txt file. This
file is the input into the FetchScriptGenerator.
The FetchScriptGenerator outputs two files: pluginVersions.properties and
featureVersions.properties.
It is these two files that the BuildScriptGenerator uses to replace the
qualifiers. So your BIRT versions tools should update these files instead
of the directory.txt
-Andrew
----- Forwarded by Kim Moir/Ottawa/IBM on 10/20/2006 02:34 PM -----
"Xiaoying
Gu" <xgu@xxxxxxxxxxx>
10/19/2006 04:27 AM
|
To
|
Kim Moir/Ottawa/IBM@IBMCA
|
cc
|
"Sue Lee"
<slee@xxxxxxxxxxx>
|
Subject
|
RE: Fw: questions about the
BIRT build system
|
|
Hi Kim,
Sorry for bothering again.
I have a question about the version control again.
Since BIRT’s CVS tagging is not performed by the developers, so what I
plan to do now is:
1. Check out from HEAD according to the map file. I use
<plugin.name>=HEAD in the map file.
2. Use BIRT version tools to generate cvs diff log and update the
“HEAD” in directory.txt with the real version (like
v20061017-0630).
3. Run the generate script target to generate the build.xml of each
plugin. ( I did NOT set the property ${forceContextQualifier})
According to the wiki, I thought the version should be get from map file. So
they should be replaced with the replaced value in directory.txt.
But it seems the replacement still use the current timestamp.
Is there anything I missed? Or modifying directory.txt is not enough?
Thanks,
Xiaoying _______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev