[
https://jira.codehaus.org/browse/MRELEASE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327573#comment-327573
]
Robert Scholte commented on MRELEASE-694:
-----------------------------------------
Please confirm that this has been fixed with version 2.4+ due to the
refactoring for MRELEASE-511. A lot of tests have been written resulting in
almost 100% code coverage for the {{MapVersionsPhase}}
> -SNAPSHOT is unexpectedly appended to version in branched pom.xml
> -----------------------------------------------------------------
>
> Key: MRELEASE-694
> URL: https://jira.codehaus.org/browse/MRELEASE-694
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.1, 2.2
> Environment: apache-maven-2.2.1
> Reporter: Ken Alexandersson
> Priority: Critical
> Attachments: pom.xml.branch, pom.xml.next, pom.xml.releaseBackup
>
>
> When running the following
> {{mvn org.apache.maven.plugins:maven-release-plugin:2.2:branch
> -DbranchName=ROOT_1.0_RB -DupdateBranchVersions=true
> -DautoVersionSubmodules=true -DdryRun=true -DreleaseVersion=1.0
> -DdevelopmentVersion=1.1-SNAPSHOT}}
> the branched pom.xml gets the version "1.0-SNAPSHOT" instead of expected
> "1.0" (please see attached poms for details). Trying to add
> {{-DupdateVersionsToSnapshot=false}} does not help either.
> Side note: Did a run in interactive mode (by leaving out
> {{-DreleaseVersion=1.0}} and {{-DdevelopmentVersion=1.1-SNAPSHOT}}, which
> produced an expected result where the submitted versions were reflected
> correctly in the pom-files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
