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.
dev build 200512011936 On startup, Netbeans rescans the classpath for changes and iterates through the contents of JAR files on the classpath even if they have not been modified since the last time it scanned the classpath. I am expecting Netbeans to use the file last-modified timestamp to determine whether it should iterate through its contents. This would be much faster than the current approach. It could be that I am misinterpreting what Netbeans is doing and it is deciding to always rescan any Library Manager entry that has a Sources value set, though if that is the case I think that can be improved as well. For example, I've got Hibernate mounted as a JAR in the classpath tab and its sources in the Sources tab. I am expecting Hibernate to only use the Sources entries at debug time to open files. I am not expecting it to rescan these files at startup. If there is a reason this must be done please let me know what I missed ;)
Netbeans _uses_ the file last-modified timestamp to determine whether it should iterate through contents of the jar file. rt.jar and src.zip from JDK are most visible examples of this strategy.
Any idea why it rescans the classpath of libraries that have both a JAR and source-files mounted? I was under the impression that source-files are only used during debugging, and do not actually affect the classpath.
Reorganization of java component