This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I was unable to delete a jar file from a CVS filesystem after mounting it once. The build Script created a jar file in one the CVS directory and after I mounted it once I wasn't able to delete it until I shut down the IDE. (Reproducable). org.netbeans.modules.vcscore.VcsFileSystem$12: Cannot delete VCS file deploy/lib/jce1_2_1.jar in CVS D:\-=[DATEN] =-\PRIVAT\Sourceforge\src\SecureDataManager\sdm\build. at org.netbeans.modules.vcscore.VcsFileSystem.delete (VcsFileSystem.java:3183) at org.openide.filesystems.AbstractFileObject.delete (AbstractFileObject.java:480) at org.openide.loaders.FileEntry.delete (FileEntry.java:100) at org.openide.loaders.MultiDataObject.handleDelete (MultiDataObject.java:422) at org.openide.loaders.DataObject$3.run (DataObject.java:530) at org.openide.filesystems.EventControl.runAtomicAction (EventControl.java:89) at org.openide.filesystems.FileSystem.runAtomicAction (FileSystem.java:416) at org.openide.loaders.DataObject.delete (DataObject.java:528) at org.openide.loaders.DataFolder.handleDelete (DataFolder.java:592) at org.openide.loaders.DataObject$3.run (DataObject.java:530) at org.openide.filesystems.EventControl.runAtomicAction (EventControl.java:89) at org.openide.filesystems.FileSystem.runAtomicAction (FileSystem.java:416) at org.openide.loaders.DataObject.delete (DataObject.java:528) at org.openide.loaders.DataFolder.handleDelete (DataFolder.java:592) at org.openide.loaders.DataObject$3.run (DataObject.java:530) at org.openide.filesystems.EventControl.runAtomicAction (EventControl.java:89) at org.openide.filesystems.FileSystem.runAtomicAction (FileSystem.java:416) at org.openide.loaders.DataObject.delete (DataObject.java:528) at org.openide.loaders.DataNode.destroy (DataNode.java:215) at org.openide.nodes.FilterNode.destroy (FilterNode.java:399) at org.openide.explorer.ExplorerActions$DeleteActionPerformer$ DestroyAtomic.invoke(ExplorerActions.java:531) at $Proxy5.run(Unknown Source) at org.openide.filesystems.EventControl.runAtomicAction (EventControl.java:89) at org.openide.filesystems.FileSystem.runAtomicAction (FileSystem.java:416) at org.openide.explorer.ExplorerActions$DestroyInvoker.run (ExplorerActions.java:565) at org.openide.explorer.ExplorerActions$DeleteActionPerformer. doDestroy(ExplorerActions.java:506) at org.openide.explorer.ExplorerActions$DeleteActionPerformer. performAction(ExplorerActions.java:476) at org.openide.util.actions.CallbackSystemAction.performAction (CallbackSystemAction.java:108) at org.openide.util.actions.CallableSystemAction.actionPerform ed(CallableSystemAction.java:69) at org.netbeans.core.ModuleActions$1.run (ModuleActions.java:100) at org.openide.util.Task.run(Task.java:136) [catch] at org.openide.util.RequestProcessor$Processor.run (RequestProcessor.java:599)
It seems, that java.io.File.delete() returned false on that file. Perhaps the file was locked by some other process in Windows? Were you able to delete the file in Windows? If java.io.File.delete() returns false, I can not do anything with it. Thus closing as "wontfix".
Verified until Constantin provides us with required information.
I was only using netbeans during the whole time. I wasn't able to delete this file from windows during this time either. I had to close Netbeans in Order to delete this file. Windows told me that some other process had a grab on this file. But as soon as I closed Netbeans I was able to delete the file. Just saw that it probably isn't a VCS bug but more one of the Jar File Filesystem. Since the same error occus when trying the same on a local directory.
Thanks for the additional info. From what did you describe it really seems like a Jar File Filesystem problem. Moving to openide...
Changed the summary to better suit to the problem.
this is a well known problem of the current impl of JarFileSystem. We use JDK's impl of jar handling which keeps locks on jar file much longer than necessary.
*** This issue has been marked as a duplicate of 20743 ***
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.