Community
Participate
Working Groups
Build Identifier: 3.6.0 The Ant Editor does not support the "extension-point" feature, introduced in Ant 1.8. This functionality is required for Ant 1.8.* and Eclipse integration (https://bugs.eclipse.org/bugs/show_bug.cgi?id=302296). Reproducible: Always Steps to Reproduce: 1. Install org.apache.ant_1.8.1.zip from https://bugs.eclipse.org/bugs/show_bug.cgi?id=302296 2. Execute the following build script: <project default="ep-B"> <target name="A" /> <extension-point name="ep-B" depends="A" /> <target name="B" extensionOf="ep-B" depends="D" /> <target name="C" depends="ep-B" /> <target name="D" /> </project>
Created attachment 178301 [details] Patch for ant1.6.2.dtd This patch covers the content assist related issue.
Created attachment 200545 [details] A patch Michael, Please look at the patch and give me your comments.
Created attachment 200651 [details] Proposed patch + regression test This patch also fixes Shift+F2 on extension-point also. Also note that both this patch and the patch in comment 2 are on top of the patch given in comment 1. With this patch, I think the only left over now is having a template for extension-point.
The patch works nicely. The only issue I found was that you do not get a completion proposal for "extension-point" when you activate content assist on a blank line. Consider the following example: <?xml version="1.0" encoding="UTF-8"?> <project name="project" default="default"> <description> test project </description> <target name="default" description="test target"> </target> </project> Steps 1. place the caret on line 6 (the blank line) 2. do not type anything 3. activate content assist 4. start typing extension-point I would expect one of the proposals to be 'extension-point'.
(In reply to comment #4) Mike, nice-catch. I will update a new patch shortly.
Created attachment 200745 [details] Proposed patch + regression test Updated the fix to support getting the extension-point in the content-assist.
Works perfectly. Applied to HEAD.
verified.
*** Bug 359456 has been marked as a duplicate of this bug. ***