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 117843 - Greater Control Over Project Scanned Requested
Summary: Greater Control Over Project Scanned Requested
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: Sun Solaris
: P3 blocker with 1 vote (vote)
Assignee: Rastislav Komara
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-04 20:26 UTC by gglazer
Modified: 2009-07-07 21:06 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description gglazer 2007-10-04 20:26:06 UTC 
There have been many cases where people have complained about the time it takes for project scanning (e.g., issue
#116477 ).  Rather than address this from an optimization perspective, the suggestion is to address it from a UI one. 
Basically, one should be able to check a box and set a preference for opening projects (or starting nb) that says "Do no
scanning."  The understanding is that no features that depend on scanning or compiling will work correctly until a scan
is done.  Thus, matching this preference there should be a control which says "Scan Now" which allows the IDE to catch
up when the user is ready for that and also to force scanning when something has changed outside of the IDE (e.g., file
perms changing due to the action of an external change management system).
Comment 1 gglazer 2007-11-18 23:49:05 UTC 
Same goes for task scanning, which also slows things down at what seem to be random intervals.
Comment 2 Jesse Glick 2009-07-07 21:06:52 UTC 
There is a module on auto update that does just this.