[
https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315408#comment-315408
]
Michael Wenig commented on MRELEASE-594:
----------------------------------------
I ran into this problem today. I released a organization-parent-pom which still
had a SNAPSHOT-dependency in dependencyManagement. After that I tried to
release the using project and this fails because of the usage of a SNAPSHOT. So
I either have the possibility to redefine the version in the using project
(which makes the predefinition in dependencyManagement useless) or to create
another release of the parent and mark the old one as "do not use"
=> I cleary see it as a bug, that the release has been possible.
I also aggree with Brett that having SNAPSHOTs in released POMs is not a good
practice - if there is a usecase for that I would suggest a parameter which has
to be explicity switched on
Ist there any schedule for this issue?
> release:prepare should stop when there is snapshots in dependencies management
> ------------------------------------------------------------------------------
>
> Key: MRELEASE-594
> URL: https://jira.codehaus.org/browse/MRELEASE-594
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Reporter: Thomas Bruyelle
> Assignee: Olivier Lamy
> Fix For: Backlog
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
