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.
Product Version = NetBeans IDE 7.3.1 (Build 201306052037) Operating System = Windows 7 version 6.1 running on amd64 Java; VM; Vendor = 1.7.0_21 Runtime = Java HotSpot(TM) 64-Bit Server VM 23.21-b01 In a project which has many libraries included, often when trying to "clean and build" the project will fail because Netbeans removes the compiled jar file of a library, but fails to recompile the library and reports an error. Most likely because background scanning is in progress. Could this be handled in a more sophisticated manner, because it becomes very annoying especially when just one library from the project that includes is adjusted, p.e. with refactoring a class. Often multiple retries simply do not solve the problem. Also the order in which libraries are deleted and recompiled is very unclear and could be set. When a library jar file is removed due the "Clean and build", it looks like a background scanning is started already, even when the changes made already completed a background scanning. Then there is the issue that from these libraries not the library but the source files are used to validate the existence of classes and routines, and thus the correctness of the source code, but again at compile and run time these lib need to be present.