Hi,
I can't make buildnumber-maven-plugin work with SVN 1.7.
I thought it was fixed in MBUILDNUM-79.
Now that maven-scm-provider-svnjava:2.0 is out, I tried to add it as
dependency of the buildnumber-maven-plugin but I don't think it actually
uses it.
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.1</version>
<configuration>
<providerImplementations>
<svn>javasvn</svn>
</providerImplementations>
</configuration>
<executions>...</executions>
<dependencies>
<dependency>
<groupId>com.google.code.maven-scm-provider-svnjava</groupId>
<artifactId>maven-scm-provider-svnjava</artifactId>
<version>2.0</version>
</dependency>
</dependencies>
</plugin>
It's weird because when I add the maven-scm-provider-svnjava:2.0 dependency
to my maven-scm-plugin, I can update and commit without any problem.
Regards,
Xavier
Olivier Lamy wrote:
>
> The Mojo team is pleased to announce the release of the Buildnumber
> Maven plugin version 1.1
> Release Notes - Mojo Build Number Maven Plugin - Version 1.1
>
> ** Bug
> * [MBUILDNUM-79] - javasvn provider does not work for the new SVN
> 1.7 workspace format
>
--
View this message in context:
http://old.nabble.com/-ANN--Buildnumber-Maven-plugin-1.1-Released-tp33795121p33881143.html
Sent from the mojo - user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
