[ https://jira.codehaus.org/browse/MRELEASE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335431#comment-335431 ]
Markus KARG commented on MRELEASE-837: -------------------------------------- Strange to see this being closed as "Cannot Reproduce" instead of "Fixed" as it can be reproduced 100% always with 2.0.0 and you wrote yourself "Already fixed". ;-) > Release plugin resets parent to outdated version > ------------------------------------------------ > > Key: MRELEASE-837 > URL: https://jira.codehaus.org/browse/MRELEASE-837 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare > Affects Versions: 2.0 > Reporter: Markus KARG > Assignee: Robert Scholte > Priority: Critical > > Using Maven 3.0.4 I noticed that the release plugin resets the parent to an > outdated version. Here is what I noticed with all of my Projects when doing > "mvn release:prepare": > * Asks whether I want to update the parent version. I say "yes". > * Asks whether "1.1" is the correct release version of paren, which is true. > * Asks whether "1.2-SNAPSHOT" is the correct developer version of parent, > which is true. > * Asks whether "1.1" is the correct release version of child, which is true. > * Asks whether "1.2-SNAPSHOT" is the correct developer version of child, > which is true. > After perform is done, my pom has different versions for parent and child: > * Child correctly has "1.2-SNAPSHOT" > * Parent incorrectly is reset to "1.1-SNAPSHOT" > This is simple to fix in each POM, but annoying when releasing much and > often. Hence I would be glad if this could get fixed soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira