maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Štědrý (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (MRELEASE-953) release:branch non SNAPSHOT -DdevelopmentVersion is ignored
Date Fri, 10 Jun 2016 18:31:21 GMT

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

Michael Štědrý edited comment on MRELEASE-953 at 6/10/16 6:30 PM:
------------------------------------------------------------------

I found out that it was probably my mistake, because when I accidentaly used *-DdevelopmentVersion=1.4.0-SNAPSHOT*
it worked correctly ...

What made me lose considerable time researching this is a lack of a WARNING message telling
me that a NON-SNAPSHOT version will be ignored.


was (Author: vaskrist):
I found out that it was probably my mistake, because when I used *-DdevelopmentVersion=1.4.0-SNAPSHOT*
it worked correctly ...

What made me lose considerable time researching this is a lack of a WARNING message telling
me that a NON-SNAPSHOT version will be ignored.

> release:branch non SNAPSHOT -DdevelopmentVersion is ignored
> -----------------------------------------------------------
>
>                 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.4.1-2.5.3
>            Reporter: Michael Štědrý
>            Priority: Minor
>
> 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 instead
to be the new working copy version of the expected 1.4.0.
> {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)

Mime
View raw message