[
http://jira.codehaus.org/browse/MRELEASE-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse updated MRELEASE-35:
-------------------------------------
Component/s: scm
> release plugin doesn't tag correctly with svn+ssh when remote and local
> username don't match
> --------------------------------------------------------------------------------------------
>
> Key: MRELEASE-35
> URL: http://jira.codehaus.org/browse/MRELEASE-35
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Reporter: Brett Porter
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> svn is very stubborn about this. Basically you have to have the value in
> <developerConnection> match the url used to check it out.
> Things that will fail:
> - if you pass in a different username to --username, it is not passed on to
> ssh
> - if you specify a username in the ssh command it works, as long as the URL
> is the same in both. svn+ssh://[EMAIL PROTECTED]/... is considered a
> different repository to svn+ssh://foo/... even if I am bporter
> I think we can take a couple of steps:
> - for svn+ssh, put the username in the URL instead of passing --username
> - possibly check the current checkout (svn info) and derive the tag location
> from that, ignoring the local checkout OR if they don't match, relocate the
> local checkout to that of developerConnection
> - use javasvn instead
--
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
