This is an interesting patch but with its current implementation I think
it's a bit dangerous. The potential for trashing pre-set properties is
quite high. The intention of the property attribute on the loop task was so
that you as the build author know what property is going to change. With
this change you have no idea what properties are going to be changed.
Why not take it a tiny bit further and change the 'in' behavior to take an
xml file AND xpath query and use the user supplied property as a prefix.
This way the only properties that change are prefixed with a user supplied
prefix. I also think XmlElement vs Node is a bit clearer.
Ie,
<foreach item="XmlElement" in="manifest.xml:manfest/component"
property="component">
<echo message="element=${component} name-attribute=${component.name}
path-attribute=${component.path}"/>
</foreach>
There is probably a better syntax for specifying the filename and xpath
statement (is there a standard for this?)
I really like the idea/potential I just think it needs a bit more work for
general consumption.
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
