[ http://jira.codehaus.org/browse/MRELEASE-96?page=all ]
Brett Porter closed MRELEASE-96:
--------------------------------
Assign To: Brett Porter
Resolution: Won't Fix
if you are using coordinated versioning, then the parent is always released
with the child, and this isn't a problem.
If you aren't, you should leave the parent version as the released version
until you need the snapshot. If you need the snapshot, the release plugin is
right to complain if you are using it and the parent has been released.
Hope that makes sense... we still aim to improve this without the need of the
tools in Maven 2.1.
> 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
