[
https://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315683#comment-315683
]
Darryl L. Miles edited comment on MRELEASE-594 at 12/14/12 3:34 AM:
--------------------------------------------------------------------
=> I cleary see it as a bug, that the release has been possible.
Without some kind of command line / property override you mean ?
Ideally the override for different things:
* SNAPSHOT parent/grand-parents [parent]
* SNAPSHOT plugins versions used [plugin]
* SNAPSHOT dependency versions used [dependency]
* SNAPSHOT the project(s) being the subject release itself [project]
I see all 4 are being separate matters but maybe sharing a single property
override to allow release to happen. With a string so an override might look
like:
mvn release:foo
-DallowSnapshotVersionInRelease=parent,plugin,dependency,project,all
The idea of not using an all or nothing (which is prone to human error). The
option should make the person think a little bit more about it and the solution
should not be a sledgehammer but the minimum surface area of overriding the
normal rules required to push past the problem.
As quite often I want to allow a plugin or dependency to be a SNAPSHOT (I have
no control of their versions sometimes) but never my own projects and their
parents.
Also all error/warning dialogs should indicate the nature of the SNAPSHOT i.e.
what category from the above is it in and suggest the minimum amount of
override with property to use when retrying the release. i.e. don't offer
"all" but something else.
was (Author: dlmiles):
=> I cleary see it as a bug, that the release has been possible.
Without some kind of command line / property override you mean ?
Ideally the override for different things:
* SNAPSHOT parent/grand-parents [parent]
* SNAPSHOT plugins versions used [plugin]
* SNAPSHOT dependency versions used [dependency]
* SNAPSHOT the project(s) being the subject release itself [project]
I see all 4 are being separate matters but maybe sharing a single property
override to allow release to happen. With a string so an override might look
like:
mvn release:foo
-DallowSnapshotVersionInRelease=parent,plugin,dependency,project,all
The idea of not using an all or nothing (which is probe to human error) it to
make the person think a little bit more as quite often I want to allow a plugin
or dependency to be a SNAPSHOT but never my own projects and their parents.
Also all error/warning dialogs should indicate the nature of the SNAPSHOT i.e.
what category from the above is it in and suggest the option to the use to
retry the release with the property set.
> 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
