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.

Bug 59525

Summary:	project classpaths should not be re-scanned if no changes are made
Product:	java	Reporter:	vbeffa <vbeffa>
Component:	Unsupported	Assignee:	issues@java <issues>
Status:	RESOLVED FIXED
Severity:	blocker
Priority:	P2
Version:	4.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description vbeffa 2005-06-01 23:59:19 UTC

For large projects, it's annoying to have to wait 30-60 seconds each time the
IDE starts up for it to scan project classpaths. It should use a timestamp or
something to know that there were no changes made and not have to re-scan the
classpaths.

Comment 1 vbeffa 2005-08-17 21:45:04 UTC

Also, the scanning happens when you close a project. Why??? What purpose does
that serve?

Comment 2 Martin Matula 2005-08-18 10:23:19 UTC

The rescan does check the timestamps. It does not only scan, but also
deserializes indexes. In the current dev build the scanning is a non-modal
operation so you don't have to wait. I was not able to reproduce the scanning
problem when a project is closed.

Comment 3 vbeffa 2005-08-18 18:58:13 UTC

That's cool, but is it also cancelable? When rescanning occurs, it ties up my
CPU and it's hard to do much until it finishes, so it would be useful to be able
to cancel it and rerun it manually only when I need to. Actually, it would be
even more useful to just have an option in the project properties that would let
you delay scanning until you do it manually (or build the project).