[
https://issues.apache.org/jira/browse/MRELEASE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369455#comment-16369455
]
Robert Scholte commented on MRELEASE-694:
-----------------------------------------
I've been able to reproduce the issue.
Based on the [Create a
branch|https://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html]
page it was never possible to use the releaseVersion and developmentVersion,
even though these parameters are visible in the documentation.
However, with the recent implementation it should be quite easy to support
releaseVersion and developmentVersion as well.
> -SNAPSHOT is unexpectedly appended to version in branched pom.xml
> -----------------------------------------------------------------
>
> Key: MRELEASE-694
> URL: https://issues.apache.org/jira/browse/MRELEASE-694
> Project: Maven 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 was sent by Atlassian JIRA
(v7.6.3#76005)
