Hi Kevin,
I like the nested command and it looks like it would be easy to extend
something like this into some sort of pluggable version control task.
The wrapper task would have to be generalized a bit (i.e. include a
server, port, protocol, etc. instead of a munged root value) maybe
something like:
<cvs server="foo.com"
remotepath="/blah/blah"
module="foo"
user="me"
password="come-on-in"
passfile="/blah/blah/.cvspass"
localpath="c:/blah/blah"
ssh="c:/bin">
<update clean="true">
<fileset>
<inclues name="AssemblyInfo.cs"/>
</fileset>
</update>
<update />
<tag />
<export todir="outputdir" />
</cvs>
Jarek's I think that this idea also combines use of common names instead
of option switches. I am not sure that I understand the reference to
modulo attribute names, could you please explain how the above is
different? Also I have included an example of what nested commands
might be used for. I have seen something like this in build files
however I am not sure I like it and prefer to add a build between the
update and tag. Finally this accomplishes another thing, which is
keeping the interface/ task tags that are needed to a minimum which.
Switching to something like <vcs type="cvs" /> might be even
better...but maybe I am getting ahead of myself.
Kevin, I am not sure it would be a good idea to include the
recursive="true" attribute by default. Something like this could lead
to some unexpected side effects (i.e. <update clean="true"/>). The
purge and create directories are really there to take care of some cvs
unpleasantness so I think they make sense. Also "cvs --help update"
works for my version of cvs, sorry for the ctrl-c/ctrl-v error from the
1st post.
So...where do we go from here?
Clayton
> -----Original Message-----
> From: Kevin Dickover [mailto:[EMAIL PROTECTED]
> Sent: March 15, 2004 6:18 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Nant-users] CVS update
>
>
> I am a NAnt 0.84 user and cannot use the CVS tasks because
> they do not currently support sspi (sspi support would be a
> compelling reason to move to a nightly build, otherwise we
> will stick to official releases). However, I would like to
> see the -P -d -R options turned on by default when the tasks
> start supporting my version of CVS :-). On the subject of
> global vs. command options (you were looking for cvs --help
> update -options BTW) I would like to see CVS usage in NAnt
> reflect command line CVS as much as possible. That leaves us
> in a place where the CVS command has different
> options/arguments then the update/checkout command whether or
> not that seems flakey. You might want something like this:
>
> <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...
>
> Kevin Dickover
>
> ______________________________________________________________
> __________________________________
>
> This electronic mail (including any attachments) may contain
> information that is privileged, confidential, and/or
> otherwise protected from disclosure to anyone other than its
> intended recipient(s). Any dissemination or use of this
> electronic email or its contents (including any attachments)
> by persons other than the intended recipient(s) is strictly
> prohibited. If you have received this message in error,
> please notify us immediately by reply email so that we may
> correct our internal records. Please then delete the original
> message (including any attachments) in its entirety. Thank you.
>
>
-------------------------------------------------------
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
