commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: [parent] adding buildnumber in the manifest entries
Date Sun, 11 Sep 2011 02:55:53 GMT
When you say trunk would be replaced by the tag name would that be the tag that ends with RCx?
 If so I'd have a problem with that as that tag won't exist for long.

Ralph

On Sep 10, 2011, at 6:00 PM, sebb wrote:

> On 10 September 2011 21:04, Ralph Goers <ralph.goers@dslextreme.com> wrote:
>> 
>> On Sep 10, 2011, at 10:34 AM, sebb wrote:
>>> 
>>> 
>>> I don't see what the harm is in adding the header line.
>> 
>> Before I agree with you I'd want to see what the exact definition would be.
> 
> The manifest config in the pom is:
> 
> <Implementation-Build>${implementation.build}</Implementation-Build>
> where
> <maven.build.timestamp.format>yyyy-MM-dd
> HH:mm:ssZ</maven.build.timestamp.format>
> <implementation.build>${scmBranch}@r${buildNumber};
> ${maven.build.timestamp}</implementation.build>
> 
> for example in the actual manifest.
> 
> Implementation-Build: trunk@r1163241; 2011-09-11 01:55:42+0100
> 
> obviously trunk would be replaced by the tag name.
> 
> The format and manifest header name could of course be easily changed,
> or the details could potentially be stored elsewhere in the jar.
> 
>> Ralph
>> 
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message