> <cvs cvsroot="{$CVSROOT}" rootprefix="{$CVSROOTPREFIX}" readonly="true">
> <update pruneEmpty="true" buildDirectories="true" recursive="true">
> <fileset ...>
> </update>
> </cvs>
>
> There doesn't really seem to be an elegant way to do this...
What's wrong with the following syntax (modulo attribute names)? Why do you
require the separation of global vs command options?
<cvs-update
cvsroot=":pserver:[EMAIL PROTECTED]:/cvsroot/nant"
readonly="true"
pruneEmpty="true"
buildDirectories="true"
recursive="true"
module="nant"
localDir="nant" />
Why would you want to enclose multiple cvs operations inside a single <cvs>
task? Typically you'll just want to fetch some module from some CVSROOT and
store the resulting tree in some local directory. That's all. It really
doesn't need to be more complex.
The number of options that cvs.exe supports is finite, small enough and not
very likely to change (now that we have SVN which is generally better) and
there's no reason to abstract that away.
Jarek
-------------------------------------------------------
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_id=1470&alloc_id=3638&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
