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.
"Class xxx not found" errors are very common, and most of the time the fix is to add an Import statement to the source code. It would be a really nice time-saver if Netbeans, after the occurance of such a compile error, would try to figure out if the class exists in the universe of possible imports, and if so, then offer to insert that import statement into my source file (or provide a button to press that will add it, or just add it, etc...). This would save time for nearly all Java developers, and be a nice product differentiator.
Probably better considered as part of a general "import management" feature (clean up existing imports, consolidate or split apart wildcards, etc.).
There will be probably an import tool as soon as I finish underlying support classes. However, the compiler does not - currently - distinguish "Class xxx not found errors" from other ones; output from external compilers can only be regexp-ed for some (configurable) string so the IDE will catch some special error types [what other error types are so special ? ;-) ]
Reopening
You can use Import Management Tool.
Resolved for 3.3.x or earlier, no new info since then -> closing.
Reorganization of java component