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.
The task list window shows Java errors in the open project. But I rarely have any outstanding errors, and they are usually easy to find anyway (e.g. looking at the Projects tab). The open project usually has plenty of Java warnings (both standard ones javac would report, and special NB hints) that I sometimes want to browse through and try to correct. But the task list does not show these; I have to either do an Ant clean build (for javac warnings only), or open every Java source in the project one by one and look for a yellow box.
Two separate requests: -showing compiler warnings (that would be show in the editor, as selected in the Tools/Options/Editor/Hints/Java/Standard Javac Warnings, see also issue #76702). In 6.7 and previous versions, there was a bug that prevented this from working, fixed in trunk, see: http://hg.netbeans.org/main-silver?cmd=changeset;node=bd21440a422e -showing results from NetBeans hint system. Unfortunately not trivial (first, computing hints is very time consuming task; second, change in one file can fix a hint/warning in another file, and there is currently no mechanism to detect this situation). This is not a defect.
http://stackoverflow.com/questions/2293408/is-there-a-way-to-list-netbeans-editor-hints
(In reply to comment #1) > Two separate requests: > [snip] > -showing results from NetBeans hint system. Unfortunately not trivial (first, > computing hints is very time consuming > task; second, change in one file can fix a hint/warning in another file, and > there is currently no mechanism to detect > this situation). This is not a defect. I would think that fixing a syntax issue could also resolve multiple problems, too.
I moved back to NetBeans recently after a few years on Eclipse and this is just about the only feature that I miss. Being able to quickly see all the hints for a project in one place is really useful when upgrading a project from, for example, Java 1.4 to Java 6 as it means I can tackle all of one type of issue at a time. As stated fixing one hint can cause others to be automatically fixed and rescanning the whole project every time a hint changes isn't a viable solution but re-scanning a class on opening should be possible. Worst case scenario is the user opens a hint message to find it's already fixed because the message was stale - perhaps show a "ghost" message for a few seconds to indicate to the user the problem has already been fixed. Combined with a slow background re-scanning and a user forced full scan I think a global hint list would stay fresh enough to be useful.
Would it at least be possible to show all warnings for the currently edited file, if not for the entire project, or for all open project?
Re. "showing results from NetBeans hint system" - I assume that if this gets implemented and an Error Hint is added to a file then not only that error will be visible in the TaskList but the file (and all parents) will be automatically annotated with standard error badge. Would you agree or should I file a separate issue for error badging?
(In reply to comment #6) > [...if] an Error Hint is added to a file then not only that error will > be visible in the TaskList but the file (and all parents) will be automatically > annotated with standard error badge That would also be my expectation, and probably the expectation of anyone accustomed to domain-specific Eclipse builders.
*** This bug has been marked as a duplicate of bug 135014 ***