[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-760. ----------------------------------- Resolution: Fixed Joeri, I'll close this, since the original issue was fixed. Concerning your wish to keep development versions locked on the release version, there are a few reasons why I think this is not good practice: - This would mean that the same version could be build + deployed multiple times, so in fact it is a new artifact. For this reason most repository-managers won't allow you to deploy the same artifact twice by default. - Best practice is to base your project structure on a release-cycle: projects which must be released at once are part of a multi-module tree. So in our case seperate implementation from API modules. - Versions are cheap and is much easier to manage modules with the same version, even if there's no code change. At least with non-bugfix releases it would probably be better if all versions are in sync, so the user knows for sure all artifacts are part of the same delivery/shipment. - No codechange doesn't mean that the build-result will still be the same. Recently we've discovered usecases which confirms this. Mark Struberg is working on a new strategy called 'incremental builds' which should solve such issues. If you still think there's enough reason to implement your wish, please create new issue. > 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