You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bruno Medeiros (JIRA)" <ji...@codehaus.org> on 2009/10/21 22:22:26 UTC
[jira] Commented: (MRELEASE-350) Option '0' for "specify the
selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports
4:Extensions ):" is broken
[ http://jira.codehaus.org/browse/MRELEASE-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195501#action_195501 ]
Bruno Medeiros commented on MRELEASE-350:
-----------------------------------------
I can confirm that bug, with option 1 all works fine.
> 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