Bug 282516 - Consolidate compiler task tags to allow common presentation
Summary: Consolidate compiler task tags to allow common presentation
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-06 09:06 EDT by Thorsten Möller CLA
Modified: 2019-09-06 16:11 EDT (History)
1 user (show)

See Also:


Attachments
Preferences dialog with various places to configure task tags (24.85 KB, image/png)
2009-07-06 09:11 EDT, Thorsten Möller CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Möller CLA 2009-07-06 09:06:37 EDT
There are several Eclipse plugins/features available meanwhile that all allow to configure task
tags (TODO, FIXME, ...), each at different places in the preferences dialog. Since this is getting
too annoying to do it for each feature separately, they should all be consolidated in *one* place
of the preferences dialog.
Comment 1 Thorsten Möller CLA 2009-07-06 09:11:01 EDT
Created attachment 140865 [details]
Preferences dialog with various places to configure task tags

to illustrate what is meant
Comment 2 Susan McCourt CLA 2009-07-08 16:20:38 EDT
This is really a symptom of the component-based nature of Eclipse.

While it sounds simple enough to put everything in one dialog, the real issue here is that different plug-ins are defining their own compiler task tags and therefore providing their own preference UI for defining them.  In order to build a generic "task tag" UI, there would have to be some generic concept of task tags at the core level (an extension point similar to markers that would allow different plug-ins to register the tag strings).  

Additional questions are whether deeper sharing would be desired - that the same text could be interpreted by all compilers as a task tag when appearing in a comment.  There would then be a migration path for the various compilers to honor these settings.

If all of this existed, then a common UI could be built that allowed the user to define these common tags.

Moving to platform resources for comment.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:11: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.