Hi Jeff, > 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?
You can do something very close to what you want using the buildnumber-maven-plugin. As Roy says, it will embed the SCM revision rather than the SNAPSHOT timestamp, but then you can trace it back to the code. Here is how we do it in my projects: https://github.com/scijava/scijava-common/blob/78ac31345e55e509ca44b5a416b83c79bec12bb6/pom-scijava/pom.xml#L161 https://github.com/scijava/scijava-common/blob/78ac31345e55e509ca44b5a416b83c79bec12bb6/pom-scijava/pom.xml#L213 Regards, Curtis On Wed, Jun 12, 2013 at 1:17 PM, Jeff <[email protected]> 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> !! >
