[
https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315693#comment-315693
]
Michael Wenig commented on MRELEASE-594:
----------------------------------------
bq. => I cleary see it as a bug, that the release has been possible.
bq. Without some kind of command line / property override you mean ?
Yes - I did not specify any special property. It would be ok if I had specify
some property like "allowSnapshots".
As we have a controlled environment for the release plugin it would be
sufficient at our site to have an optional parameter to disallow
Snapshot-Releases.
bq. mvn release:foo
-DallowSnapshotVersionInRelease=parent,plugin,dependency,project,all
In the case it is needed at all this kind of solution would be perfect:
* The (imho normal and widespread) usecase of not allowing any SNAPSHOT in a
release at all would be supported by default
* The ones who need SNAPSHOTS in released poms would be able to do it (even I
still not fully understand the mentioned use case)
* I have to explicitly state that I want to allow SNAPSHOTS
* I am able to selectivly allow SNAPSHOTS
* Indeed the need to explicitly specify an option to allow SNAPSHOTs should
make people think about it if they are really using a reasonable process
Regards Michael
> 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
