[
https://issues.jboss.org/browse/JBIDE-13297?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-13297:
-----------------------------------------------
Another solution:
Declare new content type for file extension 'xml'.
Register it for the Android nature.
Register it for the editor, without specifying extension for the editor.
In this case, the editor will appear only on the projects with Android nature. However,
the side effect is that for these projects all xml files will have only new content type,
so that all other editors will not recognize it and will not appear in 'Open
With...' at all.
So, there is choice between
1. Content descriptor, that cannot recognize all kinds of ADT xml files,, unless some
namespace will be provided for them.
2. Separate ADT projects, so that all xml files in them can be opened _only_ by ADT's
Common XML editor, while in other projects it will not interfere.
Prevent from associating xml files to Android xml editor
--------------------------------------------------------
Key: JBIDE-13297
URL:
https://issues.jboss.org/browse/JBIDE-13297
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: upstream
Affects Versions: 4.0.0.Final
Reporter: Stefan Bunciak
Assignee: Viacheslav Kabanovich
Fix For: 4.1.2.Final, 4.2.0.Alpha1
After installing the Android Development Tools into JBDS/JBT all xml files gets
associated to Android Common Xml Editor, even pom.xml files which we used to open with the
Maven POM Editor. This issue was discussed with Burr Sutter on Face2Face that it should be
fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira