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]
