[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ 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 wi

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304232#comment-304232 ] Joeri Leemans edited comment on MRELEASE-760 at 7/20/12 11:09 PM: -

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304232#comment-304232 ] Joeri Leemans edited comment on MRELEASE-760 at 7/20/12 11:10 PM: -

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ 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 w

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304176#comment-304176 ] Robert Scholte commented on MRELEASE-760: - Why do you expect it to be 1.0? It's the next

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joeri Leemans reopened MRELEASE-760: Retested with plugin version 2.3.2 with the testcase mentioned in the original description. When

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ 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

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MRELEASE-760: - > updateWorkingCopyVersions=false still bumps up pom versions to next > development version

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Petrelli updated MRELEASE-760: -- Attachment: mrelease760-patch.diff The bug is still there even with the current fix, that

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-760. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in [r1344903