Hi,
-1000 for the framework idea :-). Okay I am going to try to put my
bruised ego aside and pull something constructive from this :-).
Framework aside for now the issue is: what syntax do you prefer:
1) option collections (current):
<cvs-update globaloptions="-nt"
commandoptions="-r VERSION_FOO" ...... >
<globaloptions>
<option name="readonly" value="true"/>
</globaloptions>
<commandoptions>
<option name="pergeempty"
value="false"/>
<option name="newdirs" value="false"/>
</commandoptions>
<fileset>
<includes name="**/*.cs"/>
</fileset>
</cvs-update>
2) attributes:
<cvs-update purgeempty="true"
newdirs="false"
overwritelocal="true"
extraoptions="-D ...">
<fileset>
<includes name="**/*.cs"/>
</fileset>
</cvs-update>
3) nested commands with attributes:
<cvs cvsroot="{$CVSROOT}" rootprefix="{$CVSROOTPREFIX}"
readonly="true">
<update pruneEmpty="true"
buildDirectories="true" recursive="true">
<fileset>
<includes name="**/*.cs"/>
</fileset>
</update>
</cvs>
4) I don't care, just quit spamming my mailbox and tell me when
you are done.
My vote is either for 1 or 3. Please let me know what your preference
is, if you have one.
Cheers,
Clayton
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
