There are some other issues, in ant 1.7 we hope to move from staticly adding conditions, filters etc to using <typedef/> for them. Using the new namespace rules would mean that this is obvious.
For example:
<antcontrib:if> <antcontrib:or> <antcontrib:equals arg1="a" arg2="${prop}"/> <newcondition url="http://apache.org..."/> </antcontrib:or> <antcontrib:then> <echo>succeeded!</echo> </antcontrib:then> </antcontrib>
of course <or/> and <equals/> will be added as typedef'ed conditions so the following will work in 1.7 (but not 1.6 with the new rules)
<antcontrib:if> <or> <equals arg1="a" arg2="${prop}"/> <newcondition url="http://apache.org..."/> </or> <antcontrib:then> <echo>succeeded!</echo> </antcontrib:then> </antcontrib>
Well, maybe the whole namespace support story should be postponed to 1.7 then? It does not really make much sense in its current form IMHO.
Ant 1.6 has a lot of improvements already, and Antlibs are definitely useful even without the namespace support AFAICT.
-chris
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
