I got around this by making the build-number-plugin @aggregator style. I just changed the javadoc tag in the plugin and rebuilt it.
/** * This mojo is designed to give you a build number. So when you might make 100 builds of version * 1.0-SNAPSHOT, you can differentiate between them all. The build number is based on the revision * number retrieved from scm. It only works with subversion, currently. This mojo can also check to make * sure that you have checked everything into scm, before issuing the build number. That behaviour can be suppressed, * and then the latest local build number is used. Build numbers are not reflected * in your artifact's filename (automatically), but can be added to the metadata. You can access the build * number in your pom with ${buildNumber}. * * @author mailto:[EMAIL PROTECTED] Julian Wood * @version $Id: BuildNumberMojo.java,v 1.0 Feb 7, 2006 11:43:08 AM woodj Exp $ * @goal create * @requiresProject * @aggregator * @description create a build number from scm if possible, otherwise a timestamp */ It then only increments the build number once per the entire build. Franz Garsombke -- View this message in context: http://www.nabble.com/maven-buildnumber-plugin-tf3281875s177.html#a9235485 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]