Bug 34382 - Loss of Location information for sequential task of macrodef
Summary: Loss of Location information for sequential task of macrodef
Status: NEW
Alias: None
Product: Ant
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.6.2
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-09 03:06 UTC by Darin Swanson
Modified: 2008-02-22 12:18 UTC (History)
0 users


Attachments
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 Darin Swanson 2005-04-09 03:06:46 UTC 
With the creation of the NestedSequential representation of the nested 
sequential task of macrodef, the Location from the original sequential task is 
lost.

Therefore when the MacroDef "fakes" out the new UnknownElement in getNestedTask
() it is not possible for this element to have the correct Location as it 
cannot be passed on from the nestedSequential object.

This comes into play for the Eclipse Ant debugger...the sequential task in the 
debugger stack trace always shows the unknown location.

I would request that if possible changes be made to provide the location for 
the sequential task in this case.