thanks for the reply. IIRC I didn't have this problem when I was using Oracle/BEA JRockit JVM... can someone verify that? and that bug is from JDK 1.4!?!? I wonder if it's fixed in JDK 1.6??
While a jar file is opened, a file descriptor to the file is maintained,
so that the file does not have to be continually reopened.
This is important for good performance of the JVM.
Note that this is business as usual for Windows applications.
You cannot replace any supporting files in a Windows application that are in
use, by design. An operation like replacing a dll typically requires a reboot
on Windows. You can make an argument for both ways of doing things, but
Java certainly cannot change the way Windows works.
I will likely close this as Will Not Fix.
From what I can see in the bug report, the problem is still there in Sun's JDK6.