I've configured the buildnumber plugin as follows:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-buildnumber-plugin</artifactId>
<version>0.9.5</version>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>create</goal>
</goals>
</execution>
</executions>
</plugin>
And uses it in a propertie file in src/main/resources:
version=Version: ${pom.version} - ${buildNumber}
The pom.version is replaced bij mij project version and the buildNumber
is replaced bij my SVN revision at the moment. It does use the SVN
executable, so you need SVN installed (and not only a GUI like Subclipse
or Tortoise).
Hth,
Nick Stolwijk
DCVer wrote:
Hmm, now I see that the revision number is null.. Looks like maven is
ignoring the scm tag..
Jörg Schaible wrote:
DCVer wrote on Tuesday, August 07, 2007 8:57 AM:
Thanks for all replies, but when I use this plugin I receive
the version of
my my project (e.g. 1.0-SNAPSHOT), but I would like to get somehow the
revision number of the svn version (e.g. 768). If someone commits some
changes and the revision number turns to 769 this would be
shown in some
property file or manifest file or whatever. I think this needs a
communication with svn using scm tags (I have already configured scm).
You might define a property in the POM like:
<properties>
<revision>$Revision$</revision>
</properties>
This will be updated everytime your POM is checked in. Since this is also
the case releasing the artifact, you will always have the proper svn
revision for a release within this property.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
