Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 142996

Summary: [quick fix] DCR: Link from a compile warning/error to preference for controlling
Product: [Eclipse Project] JDT Reporter: Randy Hudson <hudsonr>
Component: UIAssignee: Martin Aeschlimann <martinae>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: daniel_megert
Version: 3.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Randy Hudson CLA 2006-05-22 10:43:05 EDT 
I'm looking at a new warning "Type Safety: the method put(object, object)..." and I have no idea which compiler setting is generating this warning. Given the number of compiler options, it would nice to link from the marker to the preference page widget that controls the generation of that marker. Perhaps a QuickFix could also be used to open the preferences associated with the source.
Comment 1 Dani Megert CLA 2006-05-22 10:54:26 EDT 
Good idea.
Comment 2 Martin Aeschlimann CLA 2006-05-26 04:40:36 EDT 
Dani, maybe a link in the hover? We would need to find out which errors/warnings are optional (configurable) and then could the add a link 'Configure...'

There are existing requests to have a quick fix that opens the page and the option.
Comment 3 Dani Megert CLA 2006-05-29 04:15:46 EDT 
I see two things we could do
1) when showing temporary problems from JDT Core in a however we could 
   mix-in something like this: "This can be changed on the xyz preference page",
   where the preference page name would be a link. This link could be clicked in
   the sticky hover.
   Problem: there's currently no way/API to transform such a link into an action

2) a quick fix on the marker itself which allows to go to the preference page
   from the Problems view and the editor.
Comment 4 Martin Aeschlimann CLA 2007-04-25 05:40:40 EDT 
suggestion 2. is bug 96685
Comment 5 Dani Megert CLA 2008-03-26 12:22:22 EDT 
We won't provide quick fixes for that.

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