You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Štědrý (JIRA)" <ji...@apache.org> on 2016/06/10 16:57:21 UTC
[jira] [Comment Edited] (MRELEASE-953) release:branch does not
reflect -DdevelopmentVersion
[ https://issues.apache.org/jira/browse/MRELEASE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324801#comment-15324801 ]
Michael Štědrý edited comment on MRELEASE-953 at 6/10/16 4:56 PM:
------------------------------------------------------------------
Except for the regression to 2.3.2 I could get around this bug by using this command (releaseVersion instead of developmentVersion):
{code}
mvn -DdryRun=true release:clean release:branch -DbranchName=branchName -DreleaseVersion=1.4.0 -DautoVersionSubmodules=true
{code}
That left me with version 1.4.1-SNAPSHOT (instead of 1.4.0-SNAPSHOT), but that is not a such big bump in the road.
What I don't know is if this is intended behaviour (which will stop working after a fix) or just a byproduct of a bug, since releaseVersion should be used when updating the version in the branch and not the working copy.
was (Author: vaskrist):
Except for the regression to 2.3.2 I could get around this bug by using this command (releaseVersion instead of developmentVersion):
mvn -DdryRun=true release:clean release:branch -DbranchName=branchName -DreleaseVersion=1.4.0 -DautoVersionSubmodules=true
That left me with version 1.4.1-SNAPSHOT (instead of 1.4.0-SNAPSHOT), but that is not a such big bump in the road.
What I don't know is if this is intended behaviour (which will stop working after a fix) or just a byproduct of a bug, since releaseVersion should be used when updating the version in the branch and not the working copy.
> 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.
> mvn -DdryRun=true release:clean release:branch -DbranchName=branchName -DdevelopmentVersion=1.4.0 -DautoVersionSubmodules=true
> 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)