Summary: | [ExternalTools] Ant ui does not handle ENTITY entries in all cases | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Simon Arsenault <simon_arsenault> |
Component: | Ant | Assignee: | Ryan Cooper <ryan_cooper> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | julien.fourment |
Version: | 2.0 | Keywords: | readme, ui |
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Bug Depends on: | 21595 | ||
Bug Blocks: | 18692, 20635 |
Description
Simon Arsenault
2002-06-21 13:55:28 EDT
For release 2.0, this limitation will be documented in the readme. The workaround is for people to add the "file:" protocol to their paths. For example, instead of <!ENTITY custom SYSTEM "../../custom.xml"> use <!ENTITY custom SYSTEM "file:/../../custom.xml"> Note that <!ENTITY custom SYSTEM "file:/../../custom.xml"> does not work on Linux. It has to be <!ENTITY custom SYSTEM "file:../../custom.xml"> . The ant external tool support should no longer try to parse the XML Ant build file to get the list of targets. Instead, it should call AntRunner.getTargets() in ant.core plugin. (We can drop all the code in AntUtil dealing with reading in targets, including the entity resolver code). To be fixed in 2.0.1 *** Bug 21798 has been marked as a duplicate of this bug. *** |