[ http://jira.codehaus.org/browse/MRELEASE-96?page=comments#action_63918 ]
Joerg Schaible commented on MRELEASE-96: ---------------------------------------- Hi Brett, the scenario for a Super POM is different. Think of the Super POM as vehicle that does something similar to Gump. If you have about ~100 (multi-)projects you have to keep their Super POM to snapshot to ensure, that all of them are compatible using Continuous Integration. This is escpecially true for jBoss with its unified class loader. It is the only way to detect incompatibilities in an early stage if you upgrade the version of a single dependency (in the dependency management). Using fixed versions for the Super POM will hide this problem until it is probably too late. But the version upgrade might affect in reality only ~10 of the projects, since they make direct usage of the upgraded artifact. The problem is now to release some of the projects. First I will have to release the Super POM, which is fine. Now I have to change *manually* in every other project the version of the Super POM in the parent reference to this release, use the release plugin for the standard procedure and then I may not forget to reset the Super POM's version back to the snapshot again *manually*. The first manual task is at least enforced by the release plugin, but not the last one. - Jörg > 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
