|Qualifier replacement when SCM is Git [message #768667]
||Tue, 20 December 2011 10:24
| Matthew Webber
Registered: December 2010
Our buckminster properties file specifies|
This works quite well for components that were checked out from subversion - the jars get build with names like my.plugin_1.0.0.r12345.jar. Here, 12345 is the subversion revision number for the most recent revision for that plugin.
However, it does not work at all for components that were checked out from Git - the jars get build with names like my.plugin_1.0.0.qualifier.jar.
Git of course does not have revision numbers, but I expected that the qualifier would be replaced by the SHA1 hash that Git uses as a sort of revision number equivalent.
Is there a way that I can get that to work? If not, what's the alternative? Does generator.lastModified work for Git?
|Re: Qualifier replacement when SCM is Git [message #772221 is a reply to message #771944]
||Thu, 29 December 2011 04:31
| Jesper Eskilson
Registered: July 2009
On 12/28/2011 04:56 PM, Thomas Hallgren wrote:|
> On 2011-12-28 14:37, Jesper Eskilson wrote:
>> On 12/20/2011 07:07 PM, Thomas Hallgren wrote:
>>> On 2011-12-20 16:24, Matthew Webber wrote:
>>>> Git of course does not have revision numbers, but I expected that the
>>>> qualifier would be replaced by the SHA1 hash that Git uses as a sort of
>>>> revision number equivalent.
>>> The SHA1 is useless because it doesn't reflect an increasing magnitude.
>>> Thus, using it you would get versions that are actually less than the
>>> previous one. Hence the need for lastModified rather than lastRevision
>>> when using git.
>> Wouldn't it be possible to implement a qualifier replacement which
>> extracted the timestamp from the time of the latest
>> commit (in the plugin/feature)?
> That's exactly what the lastModified does.
Powered by FUDForum
. Page generated in 0.04044 seconds