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

[jieryn (JIRA)]

jieryn commented on MBUILDNUM-95 Usage Example cause java.lang.NullPointerException TIP: You will more easily communicate with other people if when listing a page with a dozen examples you specifically call out which one you are following. Here is the actual documentation for the parameters you are using: doCheck boolean 1.0-beta-1 If this is made true, we check for modified files, and if there are any, we fail the build. Note that this used to be inverted (skipCheck), but needed to be changed to allow releases to work. This corresponds to 'svn status'. Default value is: false. doUpdate boolean 1.0-beta-1 If this is made true, then the revision will be updated to the latest in the repo, otherwise it will remain what it is locally. Note that this used to be inverted (skipUpdate), but needed to be changed to allow releases to work. This corresponds to 'svn update'. Default value is: false. revisionOnScmFailure String 1.0-beta-2 Setting this value allows the build to continue even in the event of an SCM failure. The value set will be used as the revision string in the event of a failure to retrieve the revision it from the SCM. I'll capture the NPE and change that to a generic build failure, but in my mind you are specifically telling the plugin to both fail the build with no SCM information (doXxx=true) and yet also to continue (revisionOnScmFailure). You get a nonsense result because you are bending the plugin in two opposing directions. Finally, I think it is more the Maven Way to fail the build in this circumstance.

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