Community
Participate
Working Groups
An adapter has an org.eclipse.ui.editors extension that should only be associated with files with a specific name that are within specific project types. Currently the only filtering for how a Editor is applied to a file is by its name and its content. But in this particular case it is also important what type of project the particular file is in but there is no way to filter on this when matching the editor extension with a particular file thus causing the editor to be inappropriately associated with files of the same name but in the wrong types of projects.
"within specific project types" - how exactly do you think this should be specified? Also, do you think the best way to support your use case would be a change to the editors extension point, or to the way that content types are computed?
(In reply to comment #1) > "within specific project types" - how exactly do you think this should be > specified? Note that the editors extension point is in the org.eclipse.ui plug-in, which does not depend on org.eclipse.core.resources and thus has no way to talk about projects in a workspace.
Remy is now responsible for watching the [EditorMgmt] component area.
We don't plan to add this. However, the new 'org.eclipse.ui.ide.editorAssociationOverride' extension point should fit your needs. See bug 251776 for more details. *** This bug has been marked as a duplicate of bug 251776 ***