[
https://issues.apache.org/jira/browse/MRELEASE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324758#comment-15324758
]
Michael Štědrý edited comment on MRELEASE-953 at 6/10/16 4:58 PM:
------------------------------------------------------------------
The linked issue MRELEASE-951 describes the same problem but with prepare
instead of branch.
was (Author: vaskrist):
Same problem but with prepare instead of branch
> release:branch does not reflect -DdevelopmentVersion
> ----------------------------------------------------
>
> Key: MRELEASE-953
> URL: https://issues.apache.org/jira/browse/MRELEASE-953
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.5.3
> Environment: Windows 7 Enterprise 64-bit, Java 8.0.92 64-bit, Maven
> 3.2.5, maven-release-plugin 2.5.3
> Reporter: Michael Štědrý
>
> I have a simple multimodule (1 parent, 2 child projects) using the version
> 1.1.2-SNAPSHOT in all the modules. When I use the following command I am
> offered version 1.1.3-SNAPSHOT to be the new working copy version.
> {code}
> mvn -DdryRun=true release:clean release:branch -DbranchName=branchName
> -DdevelopmentVersion=1.4.0 -DautoVersionSubmodules=true
> {code}
> I tried using older version of the plugin, and the first version that works
> OK when I went back through all the versions is 2.3.2. There I am offered the
> correct version (according to the documentation -
> http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html#developmentVersion).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
