|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example cause ... jieryn (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... jieryn (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... Martin Spamer (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... jieryn (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... Martin Spamer (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... Martin Spamer (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... Martin Spamer (JIRA)
- [mojo-dev] [jira] (MBUILDNUM-95) Usage Example c... Martin Spamer (JIRA)

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. e.g.
<configuration>
{timestamp}<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
<revisionOnScmFailure>$
</revisionOnScmFailure>
</configuration>
When I couldn't do that I wanted a to create a fail-safe setup with a sensible named the end result jar.