I extended Exec. Made for a lot less code. :-)
Other than that, we followed similar paths. Ours is invoked like this:
<vss dir="${src.dir}" command="get" project="/" recursive="yes"
autoresponse="no" output="${src.dir}/refresh.txt" />
I didn't code an option for the destination directory, because here we
always get to the project's working folder.
I'm going to print out and pore over the code you sent, because I can see at
a glance there's stuff in there I'll want to use. I'll also send (under
separate cover) a copy of my code, so you can do the same.
We ought to take this offline, so no one else has to hear us natter on about
support for a Microsoft product. :-)
----------
Craig S. Cottingham
[EMAIL PROTECTED]
PGP key available from:
<http://pgp.ai.mit.edu:11371/pks/lookup?op=get&search=0xA2FFBE41>
ID=0xA2FFBE41, fingerprint=6AA8 2E28 2404 8A95 B8FC 7EFC 136F 0CEF A2FF BE41
> -----Original Message-----
> From: Everitt, Andrew [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 23, 2000 10:05 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Call for patches
>
>
> Craig,
>
> Here is my code, it just builds a command line and then
> 'exec's the ss tool:
>
> [ snip ]
>
>You would invoke it as follows:
>
><target name="init">
> <taskdef name="vss" classname="com.xms.antext.taskdefs.MSVSS"/>
></target>
>
><vss command="get"
> srcdir="vss://myproduct/com/xms/mypackage"
> destdir="${basedir}/src/com/xms/mypackage"
> recursive="true"
> label="v1.0"/>
>
> I have ideas of extending this to support more of the
> available commands but
> don't need them yet so I haven't done it ;-). It borrows the
> StreamPumper
> from the exec task written by James Davidson to get the
> output from ss.exe
> onto the console.
>
> How did you do it??
>
> Cheers,
> Andi.
>
