[MRELEASE-35] release plugin doesn't tag correctly with svn+ssh when remote and local username don't match

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-beta-5
• Component/s: scm
• Assignee: Emmanuel Venisse
• Reporter: Brett Porter
• Created: 02/Dec/05 00:02
• Updated: 06/Apr/15 01:08
• Resolved: 21/Mar/07 15:49

Description

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://bporter@foo/... 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

Issue Links

• depends upon: SCM-217 workaround svn issue with svn+ssh scheme requiring to specify user@host and ignoring --username