- This topic has 4 replies, 4 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
Why not propose to edit XML files with the ANT-editor even when the fiel nameis not [n]build.xml[/b] ?
I usually have :
- build-test.xml : to build the Junit test and DB related task
- build-javadocs.xml : to build the javadocs and associated information
but only the build.xml can be edited with the ANT-editor (even when trying to select from the ANT-view).
\T,
Thomas,
You can associate your other files with the Ant editor by changing the file associations: Windows > Preferences > Workbench > File AssociationsThe Ant editor is extremely specialized for editing Ant files, using it as a general case XML editor would not be a good or helpful thing to do.
@support-rkalla wrote:
You can associate your other files with the Ant editor by changing the file associations: Windows > Preferences > Workbench > File Associations
Unfortunately, the file associations will not let one put a wildcard in the middle of the name. All of the build files (except for the root one of course) on the project I work on are named build.*.xml. It would be nice to be able to either:
1) When build.xml is loaded as an ANT build file, have all files imported by it automatically attached to the ANT editor, or at least:
2) Be able to put a wildcard in the file associations.
Just stating this in case you aren’t already aware; you can associate *.xml with the ANT editor, and then right click your XML file, and choose Ant Editor from the “Open with” context menu.
The next time you double click the file, it will open with the Ant editor directly.
The wildcard association limitations are eclipse limitations, but we’ll keep this in mind.
Brian.
@Support-Brian wrote:
you can associate *.xml with the ANT editor, and then right click your XML file, and choose Ant Editor from the “Open with” context menu.
Ah, I didn’t realize that that menu allowed multiple associates with a filetype. That satisfies my need at the moment — at least I only have to change this once per XML build file.
The ultimate solution would be for Eclipse/MyEclipse — when reading the Ant build file — to mark all included files as belonging to the ANT editor.
