I've changed the itemtype from "node" to XmlElement", to minimize the likelihood of overwritting other properties by mistake, the new routine will create a new property by combining the xmlelement name + attribute name. i.e.
manifest file:
<manifest name="nightly">
<component name="common" path="dev\src\common"/>
<component name="environment" path="dev\src\environment"/>
</manifest>
build file:
<foreach item="XmlElement" in="manifest.xml" property="component">
<echo message=" name=${component.name} path=${component.path}"/>
</foreach>
What do you think?
THanks,
Jorge
-----Original Message-----
From: Smith, Eric V. [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 06, 2002 5:01 PM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] Modified LoopTask...
> -----Original Message-----
> From: Jorge Bermejo [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 06, 2002 6:12 PM
> To: 'Shaw, Gerry'; '[EMAIL PROTECTED]'
> Subject: RE: [nant-dev] Modified LoopTask...
>
>
> Gerry-
> That's precisely the point, I "Do" want users to override (or
> trash) default property values whenever they need to
Maybe you should specify in the .build file the properties that could
possibly be overwritten when reading the xml file. That way, at least
you're documenting in the .build file what properties could possibly be
set, and you're "protecting" the .build file from arbitrary changes that
the xml file would make. Only those properties that the author of the
.build file (presumably the developer) specifies in advance could be set
or modified.
-------------------------------------------------------
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
LoopTask.cs
Description: Binary data
