You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2009/12/19 20:16:56 UTC
[jira] Closed: (MRELEASE-461) Add a mojo parameter for using the
new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)
in branch mojo
[ http://jira.codehaus.org/browse/MRELEASE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed MRELEASE-461.
---------------------------------
Resolution: Fixed
fix in [rev 892499|http://svn.apache.org/viewvc?rev=892499&view=rev]
SNAPSHOTS deployed.
Reopen the issue if you have any trouble.
> Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0) in branch mojo
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-461
> URL: http://jira.codehaus.org/browse/MRELEASE-461
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: scm
> Affects Versions: 2.0-beta-9
> Reporter: Orestes Garcia
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 2.0-beta-10
>
>
> Due to an issue with svn > 1.5.0, release plugin doesn't work. The scm (1.2) implements a new remote tagging mechanism as a workaround.
> This is fixed for release:prepare in MRELEASE-427
> I have the same problem when executing mvn release:branch.
> It would be useful to add the -DremoteTagging argument also when making branches.
> Thank you.
--
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