ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <>
Subject Re: <macro> and XML NS hell ;-)
Date Thu, 26 Feb 2004 10:13:48 GMT
Dominique Devienne wrote:

>>From: Peter Reilly []
>>Ah, I see, you are trying to
>>use the contents of "sources" in javc and also in bm:lsync.
>>This is indeed XML NS hell!
>>The problem is that the ns uri and local name of the Unknown elements
>>are given to the elements in the calling macro.
>>In ant 1.6.0+, the namespace of elements discovered by reflection take
>>the namespace uri of type/task that contains the element (Note this is the
>>uri and not the localname).
>>The enclosed patch will allow the namespace of nested elements to be
>>either the ant uri or the namespace of the containing type/task.
>I see this is a two liner, that even puts back in commented out code...
>What's the problem with checking it in?
>When Ant 1.6.2 being built with it ;-)
It was discussed for ant 1.6.0, but was voted down:

(option c).

>Why am I the one always falling in the XML NS traps :-( --DD


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

View raw message