You could use the buildnumber maven plugin [1] in a profile with its doCheck method to check for local modifications.
[1] http://mojo.codehaus.org/buildnumber-maven-plugin/ Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Wed, Aug 13, 2008 at 2:10 PM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > Of course the problem with that is what if there were local changes when > the > build was made? Now the SCM revision is meaningless > > On Wed, Aug 13, 2008 at 1:03 PM, nicolas de loof <[EMAIL PROTECTED]> > wrote: > > > Recent snapshot repository purge introduced issues for those of us that > > depend on a specific timestamp SNAPSHOT. This is supposed to be a valid > > usecase as supported by the release and enforcer plugins. > > > > There is no way to rebuild such jars, as we can get the sources from SCM > > according to date, but cannot build and deploy the jar with the expected > > name (manual renaming is required). > > > > Could we consider for future the option to use the SCM revision ( for SCM > > that support this option, but most of us use SVN ;-) ) in replacement to > a > > timestamp, so that a specific timestamp can easily be rebuilded at > anytime > > ? > > The version format could be "X.Y.Z-revision-ABCDE". > > > > Nicolas. > > >
