[MRELEASE-1016] mvn release:branch fails on Windows to commit changed pom in branch

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.5.3
• Fix Version/s: 3.0.0-M4
• Component/s: branch
• Environment: Apache Maven 3.3.9 ; Java version: 1.8.0_60, vendor: Oracle Corporation ; OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" ; git version 2.16.2.windows.1
• Assignee: Robert Scholte
• Reporter: Anthony Whitford
• Created: 23/Oct/18 19:01
• Updated: 11/Apr/21 17:47
• Resolved: 11/Apr/21 17:47

Description

I need to create a branch from a tag. Imagine branching from a 1.0 tag, the following should work:

git checkout project-1.0

mvn release:branch -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DautoVersionSubmodules=true -DbranchName=1.0.x -DreleaseVersion=1.0.1-SNAPSHOT

git checkout 1.0.x

Alas, the pom.xml in the new branch still references version 1.0 (not 1.0.1-SNAPSHOT), and the <scm><tag> references the tag, not the branch.

This looks like MRELEASE-881 was simply never resolved.

If I run a Dry Run, like:

mvn release:branch -DupdateBranchVersions=true -DupdateWorkingCopyVersions=false -DautoVersionSubmodules=true -DbranchName=1.0.x -DreleaseVersion=1.0.1-SNAPSHOT -DpushChanges=false -DdryRun=true

I can see the correct updates in pom.xml.branch.
Note that there are no differences between pom.xml and pom.xml.next.

Why is pom.xml.branch not being captured in the branch?

Issue Links

• is a clone of: MRELEASE-881 mvn release:branch fails on Windows to commit changed pom in branch