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 have this exception when I try to compile a file. The only workaround is to exit from IDE, then manually remove the class file, and restart. java.io.IOException: Cannot delete CVS file com/profor/sapex/saxdb/gui/Config.class in CVS E:\saxdt\dev\gui. at org.netbeans.modules.vcs.VcsFileSystem.delete(VcsFileSystem.java:1979) at org.openide.filesystems.AbstractFileObject.delete(AbstractFileObject.java:431) at org.netbeans.modules.java.CleanCompiler.deleteClasses(CleanCompiler.java:180) at org.netbeans.modules.java.CleanCompiler.compile(CleanCompiler.java:220) at org.netbeans.modules.java.CleanCompilerGroup$1.run(CleanCompilerGroup.java:82) at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:363) at org.netbeans.modules.java.CleanCompilerGroup.start(CleanCompilerGroup.java:109) at org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread$GroupCompiler.run(CompilationEngineImpl.java:255)
Hi, I found how to reproduce this bug. Create a class, compile it. Then modify the source (just enter some spaces) => the name has an asterisk to show it was modified. Then do Ctrl-Z to cancel the editing => the asterisk disappears. Then try to recompile => BINGO! I hope you can to something with these indications. Thanks!
Yes, I think I've identified the cause of this -- it is the parser reading the source file in background. I've taken some steps for delete operation on a DataObject and I'll make the same adjustments on compiler. Thanks for detailed report.
Fixed in dev-130; it was most probably caused by the same thing as delete on .java sources -- parser was holding the InputStream reading the .class file while it was being deleted. Now delete takes precedence and forcibly closes the parser's stream.
[010221_2] Verified
Resolved for 3.4.x or earlier, no new info since then -> closing.