Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8.6, 2.0-rc-2
    • Fix Version/s: None
    • Component/s: Grape
    • Labels:
      None
    • Environment:
      Using Groovy Trunk 2009-10-11 on Ubuntu 9.04 Jaunty Jackalope

      Description

      Grapes makes the assumption that a jar with a given number remains the same and so does not refresh. For released jars this is an almost reasonable assumption. For snapshot jars it is decidedly unsafe. For example say I use gpars-0.9-beta-1-SNAPSHOT and the jar source is my local Maven cache. On first use Grapes copies the jar from teh Maven cache to the Grapes cache. If I update the Maven cache with a new version, Grapes fails to take a new copy. Thus error.

        Activity

        Russel Winder created issue -
        Russel Winder made changes -
        Field Original Value New Value
        Component/s Grape [ 13810 ]
        Jochen Theodorou made changes -
        Priority Blocker [ 1 ] Major [ 3 ]
        Jochen Theodorou made changes -
        Affects Version/s 2.0-rc-2 [ 18550 ]
        Affects Version/s 1.8.6 [ 18245 ]
        Jochen Theodorou made changes -
        Affects Version/s 1.7.x [ 15538 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 13:32:57 UTC 2015 [ 1428240777691 ]
        Mark Thomas made changes -
        Workflow jira [ 12732788 ] Default workflow, editable Closed status [ 12744616 ]
        Mark Thomas made changes -
        Project Import Mon Apr 06 02:11:23 UTC 2015 [ 1428286283443 ]
        Mark Thomas made changes -
        Workflow jira [ 12970527 ] Default workflow, editable Closed status [ 12978292 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Russel Winder
          • Votes:
            6 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:

              Development