maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lyons, Roy" <Roy.Ly...@cmegroup.com>
Subject Re: Putting buildNumber into Manifest...
Date Wed, 12 Jun 2013 18:34:01 GMT
You may be even more interested in injecting the version control tool's
code identification, like say the commit hash being built from git.  Then
you can trace it back to the code directly!


Thanks,

Roy Lyons




On 6/12/13 1:17 PM, "Jeff" <predatorvi@gmail.com> wrote:

>We have a continuous deployment system that constantly triggered by SCM
>changes and builds/pushes our WAR files to our various environments.
>
>I use the maven-war-plugin to insert specifics of the artifact into the
>MANIFEST.MF.  However, the version for SNAPSHOTs is always in the form
>1.1.1-SNAPSHOT, but would like to have it include the build number that
>matches what is in our internal Maven Repository (e.g.,
>1.1.1-2013050323423-27).
>
>This might be a chicken and egg scenario, but is there a way to somehow
>use
>the buildNumber in the MANIFEST instead of the SNAPSHOT qualifier so we
>can
>easily see when troubleshooting which version is really deployed?
>
>Thanks!
>
>-- 
>Jeff Vincent
>See my LinkedIn profile at:
>http://www.linkedin.com/in/rjeffreyvincent
>I ♥ DropBox <http://db.tt/9O6LfBX> !!


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Mime
View raw message