[MRELEASE-434] Assumes scm.url is Current Directory for Remote Tagging

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.0-beta-9
• Assignee: Olivier Lamy
• Reporter: Ben Tatham
• Created: 02/Apr/09 12:03
• Updated: 28/Jul/09 18:02
• Resolved: 28/Jul/09 18:02

Description

With the addition of remoteTagging=true, based on the testing I have done, the release plugin is doing a remote tag of the url defined in the scm.url property, which I think comes from developerConnection.

If this is incorrect, and that url doesn't exist, than it fails.
If this is incorrect, and the url does exist, then the user will get unexpected results, not to mention that you just ran the tests against something different than what will be released (although they will be run again at release:perform)

Is this the intended behaviour? Or is my testing taking me to the wrong conclusions?

Issue Links

• is related to: MRELEASE-427 Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)