Bug 188982 - [Markers] markerResolutions extension point should provide ability to specify regex value for attribute matching
Summary: [Markers] markerResolutions extension point should provide ability to specify...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 194476 (view as bug list)
Depends on: 162505
Blocks:
  Show dependency tree
 
Reported: 2007-05-24 13:24 EDT by David Cummings CLA
Modified: 2019-09-06 15:35 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Cummings CLA 2007-05-24 13:24:34 EDT 
The org.eclipse.ui.ide.markerResolution extension point provides the ability to specify marker attribute values for which the resolution generator is applicable.  These values are provided as a string and are compared using string equality to the attribute values of markers.

The markerResolution extension point should optionally provide the ability to specify a regular expression for the attribute value.  This regular expression would be used to determine whether the resolution generator is applicable for a given marker, based on whether the attribute value of the marker evaluates correctly for the expression.
Comment 1 Steffen Herbold CLA 2007-11-04 10:10:18 EST 
I would also like the extension point to be more flexible.

One possiblity is by matching the marker types using regular expressions. Another one, which I would prefer, is to use this extension point programmatically and thus be able to define the supported marker type during the runtime.
Comment 2 Tod Creasey CLA 2008-01-18 10:51:42 EST 
*** Bug 194476 has been marked as a duplicate of this bug. ***
Comment 3 Susan McCourt CLA 2009-07-15 12:17:42 EDT 
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:44 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.