[
https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332916#comment-332916
]
Hans Aikema commented on MRELEASE-594:
--------------------------------------
I agree with previous commenters that DISallowing snapshots in dependencies in
the release of any project should be the default (breaking backward stability
in favor of forward build stability as no-one can predict what will change in
the snapshot version after the release of the POM, making projects that
safeguard their maintenance on 'latest released' version of a parent still run
the risk of breaking builds/releases). A released parent POM should by default
give a stable development environment to build and release on. A snapshot
parent POM may introduce all kinds of dependency-caused breaking software.
Snapshot-versions of dependencies introduced by a released parent-POM breaking
your release cycle is completely counter-intuitive to the meaning of stable
artefacts in Maven.
> release:prepare should stop when there is snapshots in dependencies management
> ------------------------------------------------------------------------------
>
> Key: MRELEASE-594
> URL: https://jira.codehaus.org/browse/MRELEASE-594
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Reporter: Thomas Bruyelle
> Assignee: Olivier Lamy
> Fix For: Backlog
>
> Attachments: allowUnusedSnapshotsInDependencyManagement.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
