Build fails when scm provider is changed to non default one
-----------------------------------------------------------
Key: MOJO-1600
URL: http://jira.codehaus.org/browse/MOJO-1600
Project: Mojo
Issue Type: Bug
Components: buildnumber
Affects Versions: buildnumber-maven-plugin-1.0-beta-4
Environment: Windows XP, JDK 1.6.22
Reporter: Maciej Jezierski
After changing default scm provider, build fails on scm error even if
<revisionOnScmFailure> is defined.
Example configuration (build fails when project is not under scm eg. is
exported from svn instead of checking out):
<configuration>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
<getRevisionOnlyOnce>true</getRevisionOnlyOnce>
<providerImplementations>
<svn>javasvn</svn>
</providerImplementations>
<revisionOnScmFailure>non-svn-build</revisionOnScmFailure>
</configuration>
After removing <providerImplementations> build runs ok with non-svn-build as
version.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
