Details
-
Type:
Bug
-
Status:
Open
-
Priority:
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
-
Number of attachments :
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.