[ https://issues.apache.org/jira/browse/MRELEASE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Whitford updated MRELEASE-1016: --------------------------------------- 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 was: git version 1.9.4.msysgit.0; Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:5 2+01:00) Maven home: D:\Dev\maven\apache-maven-3.2.1\bin\.. Java version: 1.7.0_51, vendor: Oracle Corporation Java home: D:\Dev\Java\jdk7_51_x64\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > mvn release:branch fails on Windows to commit changed pom in branch > ------------------------------------------------------------------- > > Key: MRELEASE-1016 > URL: https://issues.apache.org/jira/browse/MRELEASE-1016 > Project: Maven Release Plugin > Issue Type: Bug > Components: branch > Affects Versions: 2.5.3 > 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 > Reporter: Anthony Whitford > Assignee: Robert Scholte > Priority: Blocker > Fix For: 2.5.3 > > > I need to create a branch from a tag. Imagine branching from a 1.0 tag, the > following should work: > {noformat} > 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 > {noformat} > 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: > {noformat} > mvn release:branch -DupdateBranchVersions=true > -DupdateWorkingCopyVersions=false -DautoVersionSubmodules=true > -DbranchName=1.0.x -DreleaseVersion=1.0.1-SNAPSHOT -DpushChanges=false > -DdryRun=true > {noformat} > 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?_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)