Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 190444 - ANT: Using Import function to import a macro breaks some ant editor functionality
Summary: ANT: Using Import function to import a macro breaks some ant editor functiona...
Status: RESOLVED DUPLICATE of bug 174759
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-01 07:13 EDT by David Corley CLA
Modified: 2007-06-01 11:50 EDT (History)
0 users

See Also:

Attachments
Picture showing the bug in outline view (243.98 KB, image/jpeg)
2007-06-01 07:18 EDT, David Corley CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Corley CLA 2007-06-01 07:13:25 EDT 
I have a buildfile that uses the ant <import> statement to import another buildfile containing a macro. When the file is initially opened in Eclipse, all functionality is fine. However, once editing begins, all of the targets, taskdefs,typdefs,etc in the outline pane display a "[from null]" value after their name.
The macro declaration displays [from import ../common/macrofile.xml [from null]]
The end results of all this is that when I now click on a target, the editor does not jump to that target anymore.
When I then remove the import statement, everything works fine again, but only if I close and then re-open the file.
Comment 1 David Corley CLA 2007-06-01 07:18:41 EDT 
Created attachment 69678 [details]
Picture showing the bug in outline view

This picture shows the [from null] issue caused by the bug reported. When any of the items in the outline view are clicked, eclipse no longer jumps to them in the editor.
Comment 2 Darin Swanson CLA 2007-06-01 11:50:10 EDT 
Thank you for the bug report.
This is fixed in the 3.3 stream.

*** This bug has been marked as a duplicate of bug 174759 ***