Bug 208252 - [Markers] From Problems views, allow to change severity level by right-click
Summary: [Markers] From Problems views, allow to change severity level by right-click
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-10-31 11:28 EDT by Olivier Vierlinck CLA
Modified: 2019-09-06 16:06 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 Olivier Vierlinck CLA 2007-10-31 11:28:38 EDT
The "Problems" view shows, amongst others, the errors and warning from the compiler.

It would be nice if, by right-clicking on one item of the list, we had the possibility to change the severity of corresponding compiler checks.

For example, if we see several warning messages like
   ArrayList is a raw type. References to generic type ArrayList<E> should be parameterized [...]

By right clicking on one of them and then selecting 'Change Severity to ignore', it would do something equivalent to 
Windows->Preferences->Java->Compiler->Errors/Warnings->Generic Types->usage of raw type: set to 'Ignore'  (or error!)

Or another solution ( maybe simpler to implement? ) add a 'Show in preferences' item in right-click menu, which would open the dialog mentionned above, with pre-selected Java compiler problems

What do you think?
Comment 1 Tod Creasey CLA 2007-10-31 15:30:27 EDT
That would mean adding the preference pages for everything related to markers which we currently cannot infer.
Comment 2 Susan McCourt CLA 2009-07-15 12:17:52 EDT
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:06:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.