Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 96413

Summary: [Preferences] articulate why a given editor is locked
Product: [Eclipse Project] Platform Reporter: Kim Horne <eclipse>
Component: UIAssignee: Kim Horne <eclipse>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, eclipse, for.work.things
Version: 3.1   
Target Milestone: 3.1 RC1   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Kim Horne CLA 2005-05-24 07:59:11 EDT 
From Bug 91965:

------ Additional Comment #7 From Daniel Megert 2005-05-19 06:11 [reply] -------

Looked at it in N20050519-0010: It's good that the editor which is bound via
content type can't be removed from the 'File Associations' page anymore.

I would show the content type on the ''File Associations' page as well, either
in the list (which is probably harder and more work):

*.xml (Ant Buildfile)

or below in the 'Assiciated editors' area:

Ant Editor (locked by Ant Buildfile)
or:
Ant Editor (locked by Ant Buildfile content type)
Comment 1 Kim Horne CLA 2005-05-24 14:58:44 EDT 
Fix in HEAD.
Comment 2 Kim Horne CLA 2005-05-27 09:14:42 EDT 
Verified in I20050527-0010