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.
Got by email: <cite> create JavaApplication1 and JavaApplication2 project * add few dozens of jars to JavaApplication1 classpath (I used all jars from glassfish/modules directory; about 300) and wait for them to get scanned; so far everything is good Now if you add *single* jar to JavaApplication2 (and to make it more interesting let's use a jar which is already on classpath of JavaApplication1 and which was just scanned and should be up to date) the following happens: UI shows "Scanning Projects" going from 0 to 100% *twice* and console lists: </cite>
fixed jet-main c4f700f91f57
Integrated into 'main-golden', will be available in build *201105261343* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/c4f700f91f57 User: Tomas Zezula <tzezula@netbeans.org> Log: #198901:Non needed up to date check of jar files.
I finally got to test this. Works awesome now! No scanning is shown and that's exactly what I was expecting. Thx.
Thanks David for verification. Integrated into 7.0.1 33642f019ba3