I think the right thing, technically, is to use (b), however due to the way conditions where defined (using class extension) and due to the fact that <if> extends condition, this makes for a very ugly result. Is there a way to redefine antcontrib's <if> to make it show a syntax like (c) eventhough is using (b) rules?
I guess I do not want to just provide our own implementation, but to prove that we can offer a way for third parties to reshuffle their code a little, and gain having nice NS syntax. Ideas? Jose Alberto > -----Original Message----- > From: peter reilly [mailto:[EMAIL PROTECTED] > Sent: 10 November 2003 18:21 > To: Ant Developers List > Subject: Namespace support in ant 1.6 > > > Hi, > I would like to get some movement on the outstanding issues > if ant 1.6. > > One of the outstanding issues is what namespace to use > for nested elements of tasks. (Discovered by introspection rules). > > The choices are: > a) Use the default ant namespace, this is the current rule. > b) Use the namespace of the enclosing task or type. > c) Allow either - let the build script author choose. > > Using the if task from ant-contrib and assuming an > project tag of <project xmlns:antcontrib="antlib:net.sf.antcontrib" > as an example: > > Choice a) > > <antcontrib:if> > <or> > <equals arg1="a" arg2="${x}"/> > <antcontrib:ispropertytrue property="y"/> > </or> > <then> > <echo>both conditions are true</echo> > </then> > </antcontrib:if> > > Choice b) > > <antcontrib:if> > <antcontrib:or> > <antcontrib:equals arg1="a" arg2="${x}"/> > <antcontrib:ispropertytrue property="y"/> > </antcontrib:or> > <antcontrib:then> > <echo>both conditions are true</echo> > </antcontrib:then> > </antcontrib:if> > > > Choice c) > > (one could use a) or b) or this) > <antcontrib:if> > <or> > <equals arg1="a" arg2="${x}"/> > <antcontrib:ispropertytrue property="y"/> > </or> > <antcontrib:then> > <echo>both conditions are true</echo> > </antcontrib:then> > </antcontrib:if> > > > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
