[
https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-674.
-----------------------------------
Resolution: Fixed
Sounds to me you should use {{updateWorkingCopyVersions=false}}. MRELEASE-760
has been fixed, so this should work with the next release.
> release plugin converts explicit version to snapshot
> -----------------------------------------------------
>
> Key: MRELEASE-674
> URL: https://jira.codehaus.org/browse/MRELEASE-674
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.1
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
> Java home: i:\tools\jdk\1.6.0_23\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Bernd Mau
> Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: MapVersionPhase.patch
>
>
> I would like to use {{release:update-versions}} to explicitly update the
> versions of my multiproject. Unfortunetly the release plugin converts the
> given developmentVersion to a SNAPSHOT version. It happens in
> {{MapVersionPhase.getNextVersion()}}.
> I would expect the plugin to leave the given developmentVersion property as
> it is, because the prompt version will not be converted. Here is my command
> line:
> {{mvn release:update-versions -DautoVersionSubmodules=true
> -DdevelopmentVersion=2.0.1 -DpushChanges=false}}
> I made a patch and attached it to the issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
