[
https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-760.
-----------------------------------
Resolution: Fixed
Fixed in [r1348226|http://svn.apache.org/viewvc?rev=1348226&view=rev].
Thanks for the unit-test. I've synced the developmentVersion with the
branchVersion, which I prefer because it has less variables in the if-statement
> updateWorkingCopyVersions=false still bumps up pom versions to next
> development version
> ---------------------------------------------------------------------------------------
>
> Key: MRELEASE-760
> URL: https://jira.codehaus.org/browse/MRELEASE-760
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.3
> Reporter: Joeri Leemans
> Assignee: Robert Scholte
> Fix For: 2.3.2
>
> Attachments: maven-release-plugin-testcase.zip, mrelease760-patch.diff
>
>
> The flag updateWorkingCopyVersions (more specifically with value "false") is
> not handled correctly.
> Attached project is a simple Maven project with version 1.0-SNAPSHOT,
> depending on version 2.3 of the release plugin. It is configured with
> dryRun=true and updateWorkingCopyVersions=false.
> When running mvn:prepare (and accepting the versions that are proposed),
> you'll see that pom.xml.next file contains 1.1-SNAPSHOT (the next development
> version) instead of 1.0 (the tagged version).
--
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
