[
http://jira.codehaus.org/browse/MRELEASE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206265#action_206265
]
Patrick Phelan commented on MRELEASE-350:
-----------------------------------------
I'm surprised this issue is not of higher priority. This is a hugely
inconvenient problem. If I have a pom, say, with both a plugin which is a
SNAPSHOT and a project dependency which is a SNAPSHOT I cannot release until I
manually harden one of the versions.
> Option '0' for "specify the selection number ( 0:All 1:Project Dependencies
> 2:Plugins 3:Reports 4:Extensions ):" is broken
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-350
> URL: http://jira.codehaus.org/browse/MRELEASE-350
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Reporter: Craig
> Priority: Minor
>
> CheckDependencySnapshotsPhase.java has a bug when processing this prompt with
> the 0 option selected:
> specify the selection number ( 0:All 1:Project Dependencies 2:Plugins
> 3:Reports 4:Extensions ): 0
> When choosing 0: All, the plugin goes through the motions of asking to
> resolve snapshot dependencies, but after resolving them, fails saying there
> are still snapshot dependencies.
> This bug lies with the function resolveSnapshots relying on the function
> processSnapshot to remove resolved dependencies from the set. This works for
> all cases except 0, which creates a new dependency set
--
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
