[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304232#comment-304232 ]
Joeri Leemans commented on MRELEASE-760: ---------------------------------------- We are using a multi-module project. Let's say we start at 1.0-SNAPSHOT and do a release (release 1.0). If all modules bump up to 1.1-SNAPSHOT, then next time I do a release they'll be at 2.0, even though there may have been no changes in that module. I want to avoid a version increment if there was no change. We'd like to leave the version at 1.0. As soon as someone changes a module and commits, an SCM trigger (SVN in our case) checks whether the pom is in a SNAPSHOT version. So then it is up to the developer to change the version of the pom to 1.1-SNAPSHOT. That way versions are only incremented when there are actual changes to a module. > 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