Bugzilla – Full Text Bug Listing
| Summary: | "*.ant" file association does not provide syntax coloring | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Darin Swanson <Darin_Swanson> |
| Component: | Ant | Assignee: | Jared Burns <jared_burns> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | kai-uwe_maetzel, oimoim |
| Version: | 3.0 | ||
| Target Milestone: | 3.1 M3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Darin Swanson
Ant document setup is only applied to files that have Ant buildfile content (which is only determined for .xml files) or those extensions that are specifically registered in the ant ui plugin.xml. This is a friend of bug 64707. What meaning does it have for a user to specify an extension to be associated with an editor if the document setup participants are not applied? Is there something better the Ant integration is missing here? No, this is a real problem. (Stated as one of our major cross team issues.) With the advances in content types we will run into this kind of problem more and more. Editors in general are actually designed for documents/files of a particular content types or a set of content types. As there used to be no notion of content type in eclipse, the file extension to editor mapping was introduced. Now that eclise knows content types, we have more and more extension that are registered per content type. As soon as the user defines a new file extension to edtior (or whatsoever) mapping, which does not overlap with built-in knowledge of file extension to content type mapping, all those extensions will not be installed. Unfortunately, Darin, right now there is not much what you can do to solve the problem at your end. *** Bug 74045 has been marked as a duplicate of this bug. *** As a workaround you can add "ant" as an extension in the extension points for documentCreation and documentSetup in the plugin.xml for the org.eclipse.ant.ui plugin. Restart eclipse using -clean to pick up the changes. I am going to add this extension as several users seem to use it. Kai has provided a workaround Fixed in the AntEditorDocumentProvider.createFileInfo Left a TODO to find if the underlying support is fixed to handle these cases. Please verify Jared. Note that *.ant is not the required test case as this extension has been added to the Ant Ui doc extensions. I used *.kai :-) Verified. |