|
| Re: Version confusion [message #375904 is a reply to message #375903] |
Wed, 21 May 2008 12:19   |
|
Hi Douglas,
You need to declare the version designator in your CQUERY. Passing it as
a system property will not work.
Regards,
Thomas Hallgren
Douglas Palmer wrote:
> Hi
>
> I have been using buckminster headless to create an update site from
> eclipse feature on the HEAD of my cvs server. I now want to build an
> update site for the version of the feature on a branch. Ideally I'd
> like to do this by specifying the cvs tag as part of the buckminster
> headless command.
>
> I have tried setting the required version with the
> buckminster.version.designator vmarg and adding the following version
> converter to the cvs provider in my rmap file:
>
> <versionConverter type="tag">
> <transform fromPattern="^0\.5\.1\.qualifier$"
> fromReplacement="IDT_0_5_1_release" toPattern="^IDT_0_5_1_release$"
> toReplacement="0.5.1.qualifier" />
> <transform fromPattern="^0\.5\.2.qualifier$"
> fromReplacement="IDT_0_5_2_release" toPattern="^IDT_0_5_2_release$"
> toReplacement="0.5.2.qualifier" />
> <transform fromPattern="^0\.5\.3.qualifier$"
> fromReplacement="IDT_0_5_3_release" toPattern="^IDT_0_5_3_release$"
> toReplacement="0.5.3.qualifier" />
> </versionConverter>
>
> However when I resolve the query with '-vmargs -D
> buckminster.version.designator=0.5.3.qualifier' buckminster materialises
> the code from the tag IDT_0_5_1_release. It appears the the version
> reaching the converter is null and the first suitable tag is used
> instead. How can I specify which tag to checkout from cvs?
>
> Regards
> Doug
>
|
|
|
|
| Re: Version confusion [message #375906 is a reply to message #375905] |
Wed, 21 May 2008 12:31 |
|
Douglas Palmer wrote:
> Hi Thomas
>
> Doesn't this mean that I need a new cquery for every branch/tag that I
> want to build?
Yes, that's per design. The cquery is the mechanism you use to control
the resolution and hence, the place where you put information about
branches and tags.
If you have suggestions on how to improve this to cover your use-case,
we are of course interested in hearing about it.
> Is there any mechanism that would allow me to use the
> same buckminster maps/queries to build multiple branches/tags?
>
You can use different branches/tags on different components (using
advisory nodes) but you can't make the query map different branches at
different times.
Regards,
Thomas Hallgren
|
|
|
|
|
| Re: Version confusion [message #375909 is a reply to message #375907] |
Wed, 21 May 2008 13:03 |
|
Hi Henrik,
do you mean making the version designators of the CQUERY subject to
parameter substitution? If so, that begs the question; what other
attributes of the CQUERY and it's nodes should be subject to that? All
of them?
I'm not saying it would be a bad thing but we need to think carefully
about the property scope used for the substitution and when the
substitution takes place.
Regards,
Thomas Hallgren
Henrik Lindberg wrote:
> Thomas Hallgren wrote:
>> You can use different branches/tags on different components (using
>> advisory nodes) but you can't make the query map different branches at
>> different times.
>>
> Is it possible to solve this by using properties in the query?
> Wouldn't that create a "parameterized query"?
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03736 seconds
] 
Search
Help
Register
Login
Home
