Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
2.2.0.beta1
-
None
-
None
-
Windows XP
Eclipse Indigo
Description
If I declare a dependency on a snapshot revision of a module (with changingPattern=".*SNAPSHOT"), IvyDE is unable to retrieve the updated version into the cache if the artifact in the repository is updated after the initial resolve in Eclipse. Command-line ant builds also fail in this situation.
It appears as though Eclipse is holding a lock on the jar file in the cache, which I believe is a Windows-only problem. Using something like Process Explorer to kill the file handle allows the resolve to succeed, but it's really annoying to have to do that and I don't think the average user would even know to do it. Since IvyDE is running in
Eclipse, is there a way to have it release the lock on the jar before updating?
Also, IvyDE reports this (somewhat misleadingly) as a module not being found:
"Impossible to resolve dependencies of myOrg#myMod;1.0
unresolved dependency: depOrg#depMod;1.0.SNAPSHOT: not found"
In the Ivy Console (and if you attempt to resolve in a command-line ant build), you get a more accurate error message:
"Couldn't delete outdated artifact from cache: C:\Documents and Settings\MYUSER\.ivy2\cache\depOrg\depMod\jars\depMod-1.0.SNAPSHOT.jar"