Bug 148146 - [EditorMgmt] distinguish file associations by project
Summary: [EditorMgmt] distinguish file associations by project
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-21 21:52 EDT by Gary Horen CLA
Modified: 2019-09-06 16:19 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 Gary Horen CLA 2006-06-21 21:52:45 EDT
This request first showed up (I think) in a laundry list bugzilla entry (22953: issue 3). I'm calling it out as a separate issue to see if we can get more traction for it.

Use case: various plugin developers now want to provide editors for certain file types (e.g. xml, html, jsp). These conflict when they are installed in the same instance of Eclipse. For example, try to install the Backbase Community Edition plugin (http://www.backbase.com) alongside WTP, in the same Eclipse instance.

There needs to be some way to partition file association by project. It *could* be done at the WTP level, but I think that Bugzilla 22953 has it right: it's something that belongs at the platform level, with associations assignable at project level, by the project creation wizard.
Comment 1 Susan McCourt CLA 2009-07-09 19:09:00 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 2 Boris Bokowski CLA 2009-11-17 13:07:09 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:19:17 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.