Bug 110344 - Would be nice to be able to ACK warnings
Summary: Would be nice to be able to ACK warnings
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-22 12:35 EDT by Peter M. Murray CLA
Modified: 2005-09-22 12:35 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter M. Murray CLA 2005-09-22 12:35:30 EDT
The value of warnings in the U/I becomes diluted in cases where you want to live
with particular instances of warnings.  For instance, if you want to deprecate
an interface your code is supplying, then all the code implementing or referring
to that interface is flagged by valid warnings.  However, we actually want to
leave those warnings in place because we may have legacy users referring to that
interface and they need to migrate off of it.

It would be great if we could acknowledge warnings on a per-instance basis.  The
acknowledged warnings would suppress the percolated warning flags at the package
and directory level - but might still show as slightly different markers within
a file.  This way, the percolated warning flags retain their value.

Perhaps the acknowledged warning could contain a note from the user who ack'd it
for documentation purposes.