Bug 106531 - [EditorMgmt] Contributed editor with no icon doesn't show up in File Associations
Summary: [EditorMgmt] Contributed editor with no icon doesn't show up in File Associat...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 13:47 EDT by Jared Burns CLA
Modified: 2019-09-06 15:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2005-08-09 13:47:17 EDT
If you contribute an editor via the org.eclipse.ui.editors extension point but
don't specify an icon, the editor will not be shown as an option when defining a
File Association. There's no requirement for an editor to provide an icon and
this problem ("Why doesn't my editor show up?") is a mess to figure out.
Comment 1 Gabriel Petrovay CLA 2007-03-20 16:41:26 EDT
This bug is also present in version 3.2.2
Comment 2 Andy Gianfagna CLA 2008-01-02 16:54:44 EST
This bug is present in 3.3 as well.  When an editor is declared without an icon, an error is logged that says "Required attribute 'icon' not defined" for that extension, and the editor is not loaded.  Furthermore, the "editors.exsd" schema does not itself appear to mark the "icon" field as required, so the extension point editor doesn't annotate the field with an asterisk or throw up an error when the field is not filled in.
Comment 3 Susan McCourt CLA 2009-07-09 19:07:56 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Boris Bokowski CLA 2009-11-17 13:07:59 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:32:21 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.