[ http://jira.codehaus.org/browse/MRELEASE-96?page=comments#action_63923 ]
Brett Porter commented on MRELEASE-96: -------------------------------------- This is exactly the purpose of those other changes, but its not really the responsibility of the release plugin. I wouldn't want to change this behaviour - perhaps the best alternative is to expose the rewriting as a goal that can align versions in that way. > Improve handling of Super POM snapshots. > ---------------------------------------- > > Key: MRELEASE-96 > URL: http://jira.codehaus.org/browse/MRELEASE-96 > Project: Maven 2.x Release Plugin > Type: Improvement > Versions: 2.0-beta-3 > Reporter: Joerg Schaible > Assignee: Brett Porter > > > The main reason for a super POM is to harmonize the version of the > dependencies with a dependencyManagement section in the super pom. Therefore > all other poms will reference the super pom as parent. To ensure consistency > between a lot of POMs the super pom is/must always refered as snapshot > version. This requierement collides with the release management. The release > plugin always complains about the snapshot version of the parent. > The plugin should support the scenario by comparing the last released version > of the parent POM and replace the snapshot version on its own, if the > snapshot version of the parent has not changed compared to the last release > of the parent (i.e. only the version is different in the parent POM). > release:perform should then restore the snapshot version of the parent again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
