[
http://jira.codehaus.org/browse/MRELEASE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169886#action_169886
]
Olivier Lamy edited comment on MRELEASE-375 at 3/16/09 7:56 PM:
----------------------------------------------------------------
Workaround implemented in MRELEASE-427.
snapshots deployed
To test it you have the apache snapshots repo :
https://repository.apache.org/content/groups/snapshots
And configuring release mojo as this :
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9-SNAPSHOT</version>
<configuration>
...
<remoteTagging>true</remoteTagging>
..
</configuration>
</plugin>
{code}
was (Author: olamy):
Workaround implemented in MRELEASE-427.
snapshots deployed
To test it you have the apache snapshots repo :
https://repository.apache.org/content/groups/snapshots
And configuring release mojo as this :
{code:xml}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9-SNAPSHOT</version>
<configuration>
...
<remoteTagging>true</remoteTagging>
..
</configuration>
</plugin>
{code}
> release plugin does not work with subversion > 1.5.0
> ----------------------------------------------------
>
> Key: MRELEASE-375
> URL: http://jira.codehaus.org/browse/MRELEASE-375
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: James William Dumay
> Assignee: Olivier Lamy
> Fix For: 2.0-beta-9
>
>
> I've opened up SCM-406 and created this issue so to track this problem in the
> Release Plugin project.
--
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
