[MRELEASE-494] Should fail during release:prepare if scm:url doesn't match working copy

• Type: Improvement
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0-beta-9
• Component/s: prepare
• Environment: Subversion SCM; working in a branch
• Assignee: Unassigned
• Reporter: David M. Lee
• Created: 21/Oct/09 08:31
• Updated: 22/Dec/19 13:15

Description

The release plugin should check scm:url against the output of svn info. If they don't match, it should fail with an error.

We had a situation where the pom file in a branch was screwed up during a merge, such that scm:url was incorrect. In our case, it pointed to the trunk instead of the branch.

This caused release:prepare to silently do the wrong thing. It would still do the normal edit/commit in the working copy of the branch, but then it would do the copy using the scm:url. In our case, this meant that the tag was copied from the trunk instead of the branch.

In fact, release:perform also completed successfully; our only indication that there was a problem was the version number of the released artifacts.

We cannot set remotetagging=false due to the Subversion bug trying to copy with svn > 1.5.

Issue Links

• is duplicated by: MRELEASE-970 Check that a pom.xml exists in the <scm><connection>-folder
• is duplicated by: MRELEASE-858 Check if the SVN working copy URL matches connection URL
• relates to: SCM-741 scm:validate for svn should offer a way to check the current directory actually matches what's declared in the pom
• relates to: MRELEASE-512 SCM information should be validated