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 105054 - hints need to be placed in task list (and be more aggressive)
Summary: hints need to be placed in task list (and be more aggressive)
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Action Items (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker with 3 votes (vote)
Assignee: Jan Lahoda
URL:
Keywords:
: 105055 (view as bug list)
Depends on: 102653 228302
Blocks: 61309
  Show dependency tree
 
Reported: 2007-05-29 18:05 UTC by athompson
Modified: 2013-05-22 17:47 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description athompson 2007-05-29 18:05:35 UTC
"Tools-->Options-->Java Code-->Hints" allows you to add hints for various
conditions, and to specify if the hints should be treated as warnings or errors.

all warning/error hints should be placed in the task list and have error/warning
badges placed on the files so the problems are visible even when the file isn't
the active editor.  additionally, hints treated as errors should prevent
compilation (at least from within the IDE).
Comment 1 athompson 2007-05-29 18:06:56 UTC
*** Issue 105055 has been marked as a duplicate of this issue. ***
Comment 2 tbrantb 2008-05-17 01:26:39 UTC
It's really not pleasant to have to open each Java source file to get compiler warnings/hints. Please add them to the
tasklist with compiler errors and TODOs.
Comment 3 ebakke 2011-11-26 02:38:07 UTC
For this enhancement to work well, arguably another related enhancement would need to be implemented as well: hint settings should be stored on a project basis rather than on a userdir basis, since the set of warnings/errors that should be enabled depends on the code style for each particular project. Otherwise hint settings that might work well for one project might cause another one to fail its build.

Analogy: In traditional "make"-based build systems, warning levels are stored in the Makefile (e.g. CFLAGS="-Wall -Wsign-compare -ansi"), which is usually distributed alongside the source code.

(I'm in favor of both of these potential enhancement.)
Comment 4 athompson 2013-04-05 20:17:40 UTC
bump...
Comment 5 athompson 2013-05-22 17:46:36 UTC
The "Action Items" view covers this and works quite nicely. Thanks!