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.
Only editing one single file starts a long "scanning projects"-task I deleted the cache directory. I started netbeans. Scanning and indexing was done. I edited only one file Scanning started again I have been waiting for 359.625 ms Product Version: NetBeans IDE 6.9.1 (Build 201007282301) Java: 1.6.0_21; Java HotSpot(TM) Client VM 17.0-b17 System: Windows XP version 5.1 running on x86; Cp1252; de_DE (nb) Userdir: C:\Dokumente und Einstellungen\Koeppen\.netbeans\6.9.1
When the project is bigger in the very same scenario as described I have to wait several minutes, before the most important IDE features (like Goto Type and code completion) become available. And this means several minutes after every simple update of the file!
Same thing happens to me. I wish they would fix this.
Fixed jet-main 41985eb45913. The IDE now (7.2 dev) has enabled editor features during the scan. The big scans after single file change is caused by dependencies. When you save the file, the IDE needs to update the error badges on nodes. For any change to public API of the file (signature of non private element) the IDE needs to find out all other files which are using such a changed type and recompile it to update error badges. The scope of these files can be restricted, but the option is very good hidden. You can change it in the Tools/Options/Editor/Hints where for Language "Java" select "Dependency Scanning" and you can either disable the dependency scanning of limit the scope from "All Projects" to "Project Only" or "Source Root"