archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: Unique SNAPSHOT version and buildNumber question...
Date Mon, 17 Jun 2013 03:51:14 GMT
Hi Jeff,

If I'm understanding correctly, this is more of a Maven question, since you want it inside
the artifact before it is deployed. However, Maven determines this value at deployment time,
not build time, so it can't be baked in. The best thing to do is have your deployment or configuration
management tool take care of writing that value out somewhere alongside the application. You
can certainly leverage the Maven metadata in Archiva to do that.

- Brett

On 13/06/2013, at 7:40 AM, Jeff <> wrote:

> I'm still trying to get my head around this and hope someone here can help.
> When a SNAPSHOT build of our WAR files is deployed to Archiva, such as:
>     MyApp-1.0.0-SNAPSHOT.war
> the "SNAPSHOT" gets replaced with a unique timestamp/version number, such
> as:
>     MyApp-1.0.0-20130607.220924-2.war
> I would like to have the exact version number (e.g.,
> 1.0.0-20130607.220924-2) in the MANIFEST.MF (or some other property file)
> that can be made available in the application/service itself so we can
> determine exactly what build is deployed to tomcat.
> I've been glancing at the buildnumber-maven-plugin but I don't *think* it
> will work because I need the unique SNAPSHOT version in the MANIFEST.MF to
> correlate with the actual artifact timestamp in Archiva.
> Has anyone done this and if so how?
> Many thanks!
> -- 
> Jeff Vincent
> See my LinkedIn profile at:
> I ♥ DropBox <> !!

Brett Porter

View raw message