[GROOVY-7649] Grape.resolve() always fails after first unresolved dependency

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.4.6
• Component/s: Grape
• Assignee: Pascal Schumacher
• Reporter: Jason Plurad
• Created: 28/Oct/15 13:13
• Updated: 22/Feb/16 20:48
• Resolved: 28/Oct/15 18:55

Description

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