|
Re: How to remove hash from replaced qualifier? [message #385207 is a reply to message #385147] |
Tue, 12 May 2009 12:02 |
|
Hi Oisin,
AFAIK, there's nothing in the lastModified generator that would cause such a hash to be generated. Its designed to be
either or, i.e. if no generator is used, then you'd get the hash. What do your property settings look like and what
does the version look like before the replacement takes place?
- thomas
Oisin Hurley wrote:
> Using the lastModified generator for qualifier replacement, I can get
> qualifiers that look like
> org.eclipse.stp.policy.build_1.0.1.200905120639-1--311_16231 74_
>
> Is there a way I can instruct the lastModified generator to not
> include the odd '-1--311_1623174_' bit at the end of the qualifier? I
> understand this is some kind of a hash that is created from the content
> of the feature, which reflects the
> fact that a composed feature or plugin version may have changed,
> but I don't need that - I have the date :)
>
> I can remove this in my build scripts, but I was wondering if
> there is a way I can formally declare it to buckminster, to reduce the
> need for post-processing.
>
> --oh
>
>
>
>
|
|
|
|
Re: How to remove hash from replaced qualifier? [message #385209 is a reply to message #385208] |
Tue, 12 May 2009 13:40 |
|
Hi Oisin,
Do you have any specific properties in place to enable the generator that you pass in when you execute the Buckminster
perform command? I.e.
qualifier.replacement.*=generator:lastModified
generator.lastModified.format=yyyyMMdd-HHmm
- thomas
Oisin Hurley wrote:
> Thomas Hallgren wrote:
>> AFAIK, there's nothing in the lastModified generator that would cause
>> such a
> hash to be generated.
> Yeah, I went through the code and didn't see anything that appended
> that to the qualifier.
>
> The cquery for that particular example looks like
>
> <cq:componentQuery
> xmlns:cq="http://www.eclipse.org/buckminster/CQuery-1.0"
> resourceMap="policy.rmap">
> <cq:rootRequest name="org.eclipse.stp.policy.build"/>
> <cq:advisorNode namePattern="org\.eclipse\.stp\.policy(\..*)?"
> useTargetPlatform="false"/>
> </cq:componentQuery>
>
> And the root request feature looks like
> <feature
> id="org.eclipse.stp.policy.build"
> label="Policy Project Build Feature"
> version="1.0.1.qualifier"
> provider-name="Eclipse.org">
>
> so nothing out of the ordinary there. It's just odd - and it seems
> to only occur on the root feature, not in the included features.
>
> It's not a big deal - I've updated my Ant script to extract the non-hash
> part of the version to create site directories, so I'm happy to
> continue without any changes to the generator,
> or creating a new generator or anything like that.
>
> In case anyone wants to see how to do this, consult
> the committer.site target in
>
> http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.build/bui ld/trunk/shared/build.xml
>
>
> cheers
> --oh
>
|
|
|
Powered by
FUDForum. Page generated in 0.02261 seconds