[
http://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234770#action_234770
]
Joerg Schaible commented on MRELEASE-594:
-----------------------------------------
@Thomas: Yes, it has to. The parent is an artifact on its own defining the
versions for any shared artifact (external and internal ones) in the
organization. It is in the responsibility of the project to ensure that any of
those shared artifacts is released before the project's own release. If not,
the required shared artifacts have to be released first, the depMgmt version of
the global POM is updated and released also.
@Olivier: Yes, the release of the child will fail, but only if it depends on a
SNAPSHOT. See, in an organizational POM you manage different components that
may or may not be used together. Typically one 3rd of all our internal
artifacts (~250) stay on SNAPSHOT for minor releases of individual components
or projects. It would be a QA nightmare forcing a release for all of them and
would make the release plugin completely unusable for us. And I am quite sure
that this *is* normal for an organizational POM.
> release:prepare should stop when there is snapshots in dependencies management
> ------------------------------------------------------------------------------
>
> Key: MRELEASE-594
> URL: http://jira.codehaus.org/browse/MRELEASE-594
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: Thomas Bruyelle
> Assignee: Olivier Lamy
> Fix For: 2.1
>
>
--
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
