You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Jason Plurad (JIRA)" <ji...@apache.org> on 2015/10/28 14:14:28 UTC
[jira] [Created] (GROOVY-7649) Grape.resolve() always fails after
first unresolved dependency
Jason Plurad created GROOVY-7649:
------------------------------------
Summary: Grape.resolve() always fails after first unresolved dependency
Key: GROOVY-7649
URL: https://issues.apache.org/jira/browse/GROOVY-7649
Project: Groovy
Issue Type: Bug
Components: Grape
Affects Versions: 2.4.1
Reporter: Jason Plurad
Assignee: Paul King
When there is a failed call to {{Grape.resolve()}}, {{GrapeIvy.resolve()}} hangs onto a reference to the {{IvyGrabRecord}} for the failed dependency. When subsequent {{resolve()}} calls are made, those failed records are still there, so it will continue to fail from that point on.
https://github.com/apache/incubator-groovy/blob/GROOVY_2_4_1/src/main/groovy/grape/GrapeIvy.groovy#L563
Note that {{GrapeIvy.grab()}} cleans up correctly on a failed grab.
https://github.com/apache/incubator-groovy/blob/GROOVY_2_4_1/src/main/groovy/grape/GrapeIvy.groovy#L265-L268
This defect is affecting the Apache TinkerPop Gremlin Console. Find more details here. https://issues.apache.org/jira/browse/TINKERPOP3-906
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)