Bug 69808 - New syntax error/warning annotation label
Summary: New syntax error/warning annotation label
Status: RESOLVED DUPLICATE of bug 83548
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-11 16:31 EDT by Aaron Hamid CLA
Modified: 2015-07-15 07:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Hamid CLA 2004-07-11 16:31:07 EDT
Eclipse has a bunch of useful heuristic syntax inspectors that analyze code and
can either set and Error, Warning, or Ignore on syntax/logic problems it finds
(empty blocks, unused fields etc.).

It would be nice to have an extra annotation type (in addition to Error,
Warning, and Ignore) like, say, "Note".

I would like to turn on these notes for informational purposes but if I set them
as Warning, then all my files and problem list is cluttered with things that
really aren't *warnings* per say, but just informational "notes".  Also, things
like the Jar exporter will consistently complain about warnings which I am then
unable to discern between "real" warnings, and those informational annotations.
 For instance, I might have declared a field that is being unused, but I did it
intentionally for the purpose of future use.  Or I might use a redundant cast
from a char to an int for documentation purposes to make it clear that I am
casting from one thing to another.  I would however like to be aware in general
of when/where I am doing this in a file.  These annotations already have spotted
some logic errors in a rather simple codebase which I assumed was bug-free.
Comment 1 DJ Houghton CLA 2004-07-12 09:16:22 EDT
I believe the user is requesting something similar to the // TODO mechanism.
Moving to JDT/Core for comment/closure.
Comment 2 Aaron Hamid CLA 2004-07-12 11:45:28 EDT
Hi there.  In fact I'm asking for something which is identical to what already
exists, except with an extra label.  The compiler options allow flagging various
pieces of code as either Error, Warning, or Ignore (ignore obviously does
nothing).  I am merely asking for an extra "label".  Call it what you want:
"Info", "Notes", "Tips", "FooBar", whatever.  The idea is that I get an extra
option in the Error/Warning/Ignore drop down box in the compiler options.  The
whole point is I can differentiate between Warnings which are *real* warnings
that I really care about and
useful-compiler-insights-which-aren't-warnings-but-are-nice-to-know-about.

A specific use case is that when I generate a jar, or simply look at my
"problems" list, it is non-useful to be presented with 30 "warnings" when really
they are just info/notes/tips/foobar that I have left enabled on purpose for
informational purposes.
Comment 3 Markus Keller CLA 2004-09-22 07:06:01 EDT
A dup of bug 47340?
Comment 4 Aaron Hamid CLA 2004-09-22 10:44:55 EDT
Yes, I think so!  I don't think any logic has to change, just add a new "Info"
label... so I can decide that Info items get highlighted in the editor, but
DON'T show up when I create jars, etc.
Comment 5 Frederic Fusier CLA 2004-10-28 05:08:24 EDT

*** This bug has been marked as a duplicate of 47340 ***
Comment 6 Dani Megert CLA 2015-07-15 07:32:18 EDT

*** This bug has been marked as a duplicate of bug 83548 ***