Hello Yolan,
not sure if it helps
may be ommit the command attribute, and use a nested <commandline/> tag
instead like this :
<commandline>
<argument value="log"/>
<argument value="-rp127065_0"/>
<argument value=" -S"/>
</commandline>
In other words, I wonder whether the "command" attribute does not send
all the arguments as one, causing them to be ununderstandable for the
cvs command line client.
Antoine
Aaron Jackson wrote:
I'm trying to run the cvs log -r[tag_name] -S command in ant. Log
requires that there be a module checked out in what ever directory your
running from. For some reason when I run the ant script it doesn't seem
to recognize that the revision exists in the module (the command works
in wincvs). I've included the scripts below.
<target name="get_conflicting_files" >
<cvs
cvsRoot=":pserver:${cvs.username}:[EMAIL PROTECTED]:/cvs"
failonerror="false"
command="log -rp127065_0 -S"
output="history.txt"
/>
</target>
Thanks,
Yolan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
