Unique qualifiers for features [message #467887] |
Mon, 03 August 2009 09:58  |
Eclipse User |
|
|
|
Hi,
It's really cool that you can get buckminster to use the subversion revision
number as a plugins version qualifier. I do this with the following
properties which I borrowed from the MailApp tutorial.
qualifier.replacement.*=generator:lastRevision
generator.lastRevision.format=r{0,number,00000}
The way I understand it the feature version has to be incremented so that
during software update it is recognized as having new functionality. However
the feature doesn't change in version control even if the plugins it
includes do. I'd like to have a nightly update site so I'm wondering if
there is a way to use use a timestamp for features and a revision number for
plugins? Or any other mechanism you think would work?
Thanks,
Tas
|
|
|
Re: Unique qualifiers for features [message #467896 is a reply to message #467887] |
Mon, 03 August 2009 10:25   |
Eclipse User |
|
|
|
Tas Frangoullides wrote:
> Hi,
>
> It's really cool that you can get buckminster to use the subversion
> revision number as a plugins version qualifier. I do this with the
> following properties which I borrowed from the MailApp tutorial.
>
> qualifier.replacement.*=generator:lastRevision
> generator.lastRevision.format=r{0,number,00000}
>
> The way I understand it the feature version has to be incremented so
> that during software update it is recognized as having new
> functionality. However the feature doesn't change in version control
> even if the plugins it includes do. I'd like to have a nightly update
> site so I'm wondering if there is a way to use use a timestamp for
> features and a revision number for plugins? Or any other mechanism you
> think would work?
>
If you use the same revision scheme for the feature, it's qualifier will be the highest revision found in its
dependencies or in itself. I.e. the feature qualifier will be bumped when one of its dependencies changes even if the
feature itself doesn't change.
Regards,
Thomas Hallgren
|
|
|
Re: Unique qualifiers for features [message #467904 is a reply to message #467896] |
Mon, 03 August 2009 11:00  |
Eclipse User |
|
|
|
I didn't realise it was that clever and assumed it just used the features
revision. That's really cool!
Thanks,
Tas
"Thomas Hallgren" <thomas@tada.se> wrote in message
news:4A76BB14.9020906@tada.se...
> Tas Frangoullides wrote:
>> Hi,
>>
>> It's really cool that you can get buckminster to use the subversion
>> revision number as a plugins version qualifier. I do this with the
>> following properties which I borrowed from the MailApp tutorial.
>>
>> qualifier.replacement.*=generator:lastRevision
>> generator.lastRevision.format=r{0,number,00000}
>>
>> The way I understand it the feature version has to be incremented so that
>> during software update it is recognized as having new functionality.
>> However the feature doesn't change in version control even if the
>> plugins it includes do. I'd like to have a nightly update site so I'm
>> wondering if there is a way to use use a timestamp for features and a
>> revision number for plugins? Or any other mechanism you think would work?
>>
> If you use the same revision scheme for the feature, it's qualifier will
> be the highest revision found in its dependencies or in itself. I.e. the
> feature qualifier will be bumped when one of its dependencies changes even
> if the feature itself doesn't change.
>
> Regards,
> Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.02882 seconds