[
https://issues.apache.org/jira/browse/IVYDE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278022#comment-13278022
]
Adam Lewandowski commented on IVYDE-305:
----------------------------------------
There is nothing in Eclipse that I can see would be actively using the file.
None of the classes in it are open in the editor, and there are no running
processes. Using Process Explorer shows that it is Eclipse.exe (not a spawned
JVM) that has a lock on the jar file, but I don't know of a way in Eclipse to
tell exactly what class/plugin caused the jar to open and lock it.
The jar locking is a relatively common problem with Eclipse (Google for
'eclipse lock jar file'). I opened this issue with IvyDE in the hopes that the
Ivy plugin could somehow have Eclipse release any locks on jar files before
doing it's resolve.
> Cannot delete outdated snapshot artifact from cache
> ---------------------------------------------------
>
> Key: IVYDE-305
> URL: https://issues.apache.org/jira/browse/IVYDE-305
> Project: IvyDE
> Issue Type: Bug
> Components: workspace resolver
> Affects Versions: 2.2.0.beta1
> Environment: Windows XP
> Eclipse Indigo
> Reporter: Adam Lewandowski
>
> 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"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
