ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Location in macrodef-ed tasks
Date Mon, 11 Sep 2006 19:38:45 GMT

I pushed setLocation down to ProjectComponent and added the reflection
logic to TaskAdapter just to realize that it doesn't help.

Most assertions are macrodef tasks and they always get their location
set to the antlib descriptor they've been defined in, which is rather

I've committed a failing testcase if anybody wants to look into it.
IMHO we should set each nested task's location to the one of the
invocation, at least if backtrace is set to false.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message