You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/04/11 17:03:00 UTC

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

    [ https://issues.apache.org/jira/browse/MRELEASE-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318885#comment-17318885 ] 

Hudson commented on MRELEASE-1016:
----------------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven-release » master #33

See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-release/job/master/33/

> 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
>            Priority: Blocker
>
> 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
(v8.3.4#803005)