[mojo-dev] [jira] (MBUILDNUM-95) Usage Example cause java.lang.NullPointerException

[Martin Spamer (JIRA)]

Martin Spamer edited a comment on MBUILDNUM-95 Usage Example cause java.lang.NullPointerException When I posted the issue (over a year ago) I was using <version>1.0-beta-4</version> and the documentation wasn't clear. Since I was using Mercurial for SCM at that time and the plugin was (seemingly) coupled to svn I was trying disable svn and do a pull from mercurial using pre-build step. The page at http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html Says "For each unique buildNumber, a properties file ( see buildNumberPropertiesFileLocation ) will be created (or read if it exists) which holds an integer, starting at 1. That number will be incremented on each access." Which suggest what I wanted to do was possible, when I couldn't get that working I was willing to settle for a fail-safe setup with a sensible named the end result jar. e.g. <configuration> <doCheck>false</doCheck> <doUpdate>false</doUpdate> <revisionOnScmFailure>$ {timestamp} </revisionOnScmFailure> </configuration> So with doCheck = false/ I'm trying to prevent the svn failure causing a build failure; because I know the plugin has no svn access. And with doUpdate = false/ I saying don't bother updating svn afer the build because again I know it won't work. Even though the default for those is false, but they were added to be explicitly (rule out documentation errors), whilest trying to figure out what was going on, to achieve my objective.

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email