Community
Participate
Working Groups
I use Eclipse to edit and test my code and then a rather complicated ant script to deploy it. This ant script depends on a JAR files ant_lib/metro.jar which isn't in the build path of Eclipse but every now and then, I can't delete this file because someone has a lock on it. When I close eclipse, the lock goes away so I suppose that Eclipse locks this file. Please don't open or lock files which are neither open in the UI nor used in the buildpath of Eclipse.
Sorry, I wasn't clear enough about this: The ant script will only copy this jar from a server onto the local disk. I'm not using it in a classpath in either Eclipse or ANT, so the bug must be somewhere in the UI. Actually, I'm not even using the Ant which comes with Eclipse :-) (When I'm happy, I have a DOS box waiting in the background where I can start the deployment with two keypresses).
We don't open JAR files in the platform. Moving to JDT, as they open and manipulate JARs that are visible in the package explorer. Aaron, if you can give more information to narrow it down, it would help to find the culprit. Do you always get the error, or only sometimes? Do you get the error after a simple startup/shutdown of Eclipse? Do you only get the error after running/debugging an application that uses the JAR? Do you have any other plugins installed that might be opening the JAR?
I don't always get the error but I can say for sure that I never saw it with 2.0. It must have crept in with a change for 2.1. I guess that it something I do but I haven't found out what. A simple startup+compile doesn't break. It has nothing to do with running the app because I can't (basically, I'm using Eclipse as an editor, build the stuff with Ant and then upload it in the ant script to the server where the environment exists to run it). I have to double-check, but I'm pretty sure that I have no additional plugins installed (I tried a couple with 2.0 but I think my 2.1 install is clean).
I did now double-check: My installation is a clean Eclipse 2.1. But here is a list of things that don't trigger the bug: - Starting Eclipse - Refreshing the Project - Opening the jar in Eclipse (double-clicking will show it as a text file!?) - Rebuilding the project - Having the jar file visible in the Package Explorer
moving to jdt.core
If the JAR isn't on the classpath then we should entirely ignore it. Please reopen once you have steps to reproduce this defect.
Timed out
The bug was gone with 3.0. You can close it for real, now.
Reopen to close as WORKSFORME.
Closing as WORKSFORME.
