[ 
https://issues.apache.org/jira/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MRELEASE-699.
-----------------------------------
    Resolution: Won't Fix
      Assignee: Robert Scholte

IMHO even the {{release:update-versions}} goal should put the project in a 
state ready for the next development cycle. If the {{release:prepare}} doesn't 
do its job good enough, we should fix it there. In the meantime you can use the 
{{versions-maven-plugin}} which is less strict.

> release:update-versions should support -DreleaseVersion too (not only 
> -DdevelopmentVersion), so it also supports not suffixing the version with 
> -SNAPSHOT
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-699
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-699
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: update-versions
>            Reporter: Geoffrey De Smet
>            Assignee: Robert Scholte
>              Labels: github-pullrequest
>         Attachments: 
> 0001-MRELEASE-699-release-update-versions-should-support-.patch
>
>
> The documentation
>   
> http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html
> states "The update-versions goal can use the same properties used by the 
> prepare goal for specifying the versions to be used."
> That's not true, as releaseVersion is not supported:
>   
> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion
> This means, that if you do this:
>   {{mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0}}
> that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to