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.
Recently been working on project to reverse engineer a database producing pojo and hibernate mapping xml file for each table in the database. In total there are over 2600 tables. A utiity project analyses the database and produces the pojo.java and hbm.xml. Output is written into the src directory of a second, library project - always cloed during execution of generator project. If I close all projects following generation, close netbeans and re-open netbeans, the compiler kicks off working on data in a project not yet open. Given that there are now 2600 pojo.java in this project, the compile takes a significant time to complete and the progam uses over 50% CPU (dual core cpu). This has to be a bug - thr compiler should not be working on a closed project. Please contact if you need more info david at bolsover dot com
Reassigning to "java".
Sorry, but I do not fully understand - do you have any projects when the scanning/compiling starts? -if no, I am not sure how this would happen - any steps to reproduce would be welcome -if yes, what is the relation ship between the opened project(s)? In some cases, it is necessary to scan/compile source roots from closed project, for example: consider two project P1 and P2 (both with only one source root, for simplicity), compiled into P1.jar and P2.jar. Sources in P2 have P1.jar on the classpath. If P2 is opened, the IDE needs to inspect sources of P1, even if P1 is not opened. If it did not inspect P1, and you would clean project P1 (so the P1.jar would disappear), all references to P1 in P2 would mark as errors.
Anything to reproduce this problem will be welcomed. When the project is closed during the scanning the scanning is not ended and it has to finish, it's already reported issue, it's due to the fact that it's very expensive to calculate the changes in active classpaths when you close or open project, the scanner has to work as a sliding task. But when the IDE was started with closed project it has no reason to scan anything.
After close the project is not sensitive on changes in the source tree but seems to be still sensitive on changes in its classpath.
moving opened issues from TM <= 6.1 to TM=Dev
*** This issue has been marked as a duplicate of 103056 ***