You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2015/04/06 11:58:12 UTC
[jira] [Closed] (MRELEASE-358) CheckDependencySnapshotsPhase fails
when resolving all dependencies
[ https://issues.apache.org/jira/browse/MRELEASE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-358.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte
> CheckDependencySnapshotsPhase fails when resolving all dependencies
> -------------------------------------------------------------------
>
> Key: MRELEASE-358
> URL: https://issues.apache.org/jira/browse/MRELEASE-358
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-7
> Reporter: Rich Seller
> Assignee: Robert Scholte
> Attachments: patch.txt
>
>
> In CheckDependencySnapshotsPhase, if '0' (All) is selected in response to the prompt "specify the selection number ..." the dependencies are not removed from the original set, so a ReleaseFailureException is thrown at the end of checkProject().
> In the attached patch the dependencies are removed from the original set, and the snapshotSet is returned from resolveSnapshots() to be checked in checkProject().
> In the tests, I implemented a custom Prompter because I don't know how to set multiple conditional responses on JMock1 mocks.
> One other change made while testing: in processSnapshot, "What is the next development version?" is set with a singleton list so a different value has been entered. I removed the list to make the supplied value the default but allow different responses. I can raise this as a separate issue if required
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)