Thanks, for more info. Mainly, I wanted to know if the Groovy Eclipse plugin is installed. It is, so it could be connected to the bug I pointed you to. The problem is caused by the Groovy compiler.
To confirm this is the same bug... you could try the following
- make sure no groovy files are open in any editor (when files are open in the editor the Groovy compiler is called upon to produce problem markers)
- turn of auto build
You could also try ununistalling the Groovy eclipse plugin and verify if this causes the problem to go away.
Be warned that as soon as any Groovy compilation gets invoked the problem may reappear (i.e. jars may get locked). This wouldn't usually be problem, unless you are on windows and trying to delete them.
The root of the problem is actually not caused by us, but is caused by URLClassLoader. You can read about it here if you are interested.
This is actually a big problem for people on Windows systems. The problem essentially is that URLClassLoader doesn't really provide API for asking it close its jars.
It isn't usually a problem for commandline tools, because they run and exit, releasing all locks. But in an IDE, which keeps running it is a big problem.
Andy (our compiler Guru working on Groovy Eclipse) is trying some very freaky things to work around this problem and fix this issue. But unfortunately there is not much that can be done if you are hitting this problem now.
Once the problem is fixed in Groovy Eclipse the situation may improve for you.
But... since we (Groovy and Grails) may not be the only ones using URLClassLoaders (they are quiet widely used by many Java tools) I can't really say whether Groovy was in fact that one that locked your jars.
This is why it may be good to check if your problem is indeed caused by Greclipse, or some other component.
I'm sorry I couldn't be more helpful. I've provided you with as much information as I know about what I guess could be your problem.
Kris De Volder -- SpringSource