Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-7649

Grape.resolve() always fails after first unresolved dependency

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.1
    • Fix Version/s: 2.4.6
    • Component/s: Grape
    • Labels:
      None

      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

        Attachments

        1. GrapeResolveFailure.groovy
          1.0 kB
          Jason Plurad

          Activity

            People

            • Assignee:
              pascalschumacher Pascal Schumacher
              Reporter:
              pluradj Jason Plurad
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: