Community
Participate
Working Groups
Currently all xml elements that represent an Ant buildfile are "typed" based on a string element type. It would be a better representation to create objects for the various element types. See XmlElement and OutlinePreparingHandler
See suggestions in bug 39231
I am investigating mirror the Apache Ant object model for our outline and code assist. It looks promising and I have a prototype working. The wins here: We can reuse the information from the AntModel prepared for the outline to do code assist. We will get Ant specific error messages from parsing the build file instead of generic XML parsing errors. Reducing the amount of parsing we do Much better code reuse in the Ant UI plugin
I marking this one implemented. There are still issues with generating correct error annotation lengths but that really is a separate bug . We now parse only once (per "dirty" state of the editor)...no more parsing to do code completion. The AntModel created for the outline is re-used for code completion. I think we should open smaller scope bug reports for remaining issues as found.
Please verify DarinW.
Verified.
*** Bug 36323 has been marked as a duplicate of this bug. ***