[MRELEASE-986] release:branch doesn't check if current project is located at it's scm location

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.5.3
• Component/s: branch
• Assignee: Robert Scholte
• Reporter: Andreas Schaller
• Created: 11/Aug/17 09:31
• Updated: 11/Aug/17 10:07
• Resolved: 11/Aug/17 10:07

Description

I accidentally had a wrong scm location in one of my projects, when then using the release:branch command to create a new branch, maven branched the scm location instead of the projects svn location.
Indeed this behavior is not wrong, but can be very confusing.

Example for my situation:
svn repository layout:

project
 |- trunk
 |- branches
     |- v1
     |- v2

In trunk there is always the newest version, the branches ar old releases.
For some accidentally merges I had the cm location for branches/v2 in the trunk.
Now I tried to branch v3 from trunk but I got the version of v2 in the v3 branch.

It would be helpful, if the release plugin could check the current working copy remote version (svn info provides the full path) and ensures, that this path is also set as the current scm location.

Issue Links

• duplicates: MRELEASE-512 SCM information should be validated