Bug 101894 - [EditorMgmt] associations: File Association changes or additions not reflected in project immediately
Summary: [EditorMgmt] associations: File Association changes or additions not reflecte...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-27 13:14 EDT by Mike Boyersmith CLA
Modified: 2019-09-06 16:08 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 Mike Boyersmith CLA 2005-06-27 13:14:41 EDT
If I add a file foo.xml to my project and then go into
Window-->preferences-->Workbench-->File Associations.
and add the association 'foo.xml' to the association list and then associate
say the ant editor with the file. I click Apply and then OK to exit this dialog
Next I go back to my project and try to open the file foo.xml, and the
associated editor doesn't open the file. Next I try to refresh the project and
open the file and it still doesn't open in the assocaited editor. Next I close
the project and reopen it and then the file will open in the associated editor. 

Expected, when I associate a file with an editor it should be immediately
reflected in my project, I shouldn't have to close and reopen the project to get
the updated associated editor.

Note I haven't tried 3.1 but my bet is that this is broke in 3.1 as well.
Comment 1 Kim Horne CLA 2005-07-05 10:54:26 EDT
As it happens, I can't reproduce this in 3.1.  :)
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:18:55 EDT
Moving Dougs bugs
Comment 3 Susan McCourt CLA 2009-07-09 19:07:48 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Boris Bokowski CLA 2009-11-17 13:03:31 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:08:54 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.