[
http://jira.codehaus.org/browse/MOJO-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180126#action_180126
]
Johan Walles commented on MOJO-1300:
------------------------------------
I worked around this issue thusly in my .pom:
<build>
<plugins>
<plugin>
<!-- Put the BZR revision number in the ${buildNumber} property -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<!-- Workaround for http://jira.codehaus.org/browse/MOJO-1300 -->
<dependencies>
<dependency>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-bazaar</artifactId>
<version>1.2</version>
</dependency>
</dependencies>
<configuration>
<!-- Workaround for http://jira.codehaus.org/browse/MOJO-1300 -->
<revisionOnScmFailure>MOJO1300</revisionOnScmFailure>
</configuration>
</plugin>
</plugins>
</build>
Doesn't get me a build number, but I *can* build after this.
Also ran into this after upgrading from SVN to BZR, thank you SVN for your long
and dedicated service :-).
> Buildnumber support for Bazaar
> ------------------------------
>
> Key: MOJO-1300
> URL: http://jira.codehaus.org/browse/MOJO-1300
> Project: Mojo
> Issue Type: Improvement
> Components: buildnumber
> Reporter: James Kingsbery
>
> My company is looking into alternative to SVN. I have a patch for adding
> Bazaar support to the build plugin, which has a unit test. I'm waiting for
> our legal department to OK the contribution.
--
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
