Try splitting up the -o and the output filename as two separate You
probably have an with two arguments which won't work since ANT
quotes the contents of the line combining them into one. Either
change to two tags or change what you have to an
---
Shawn Castrianni
-Original Message
PROTECTED]
Sent: Sunday, February 05, 2006 2:45 PM
To: Ant Users List; Harshal Chavda
Subject: Re: problem with exec task
Harshal,
"Error=2" from Windows means "file not found". You can find the full set of
all of the Windows error codes at
http://msdn.microsoft.com/library
Harshal,
"Error=2" from Windows means "file not found". You can find the full set of
all of the Windows error codes at
http://msdn.microsoft.com/library/?url=/library/en-us/debug/base/system_error_codes.asp?frame=true.
You have either misspelled the name of the file or, more likely, you have
On Mon, 23 Jan 2006, Tommy Nordgren <[EMAIL PROTECTED]> wrote:
> I want to run an executable nested in one of my build directories.
> I've tried:
>
> This executes the command, but the work directory is still the base
> directory of my build.
> I want it set to the directory containing the execut
Users List" <[EMAIL PROTECTED]>
To
"Ant Users List" <[EMAIL PROTECTED]>
cc
Subject
RE: problem with exec & rsh
Does the rsync command you are trying to run behave the same way if you
run it from the command line? I think I have seen this behavior from rsync
PROTECTED]>
To
"Ant Users List" <[EMAIL PROTECTED]>
cc
Subject
RE: problem with exec & rsh
Does the rsync command you are trying to run behave the same way if you
run it from the command line? I think I have seen this behavior from rsync
before. I think you might
Does the rsync command you are trying to run behave the same way if you run it from
the command line? I think I have seen this behavior from rsync before. I think you
might be better off trying a different strategy than calling rsync from the
task. I have automated a deployment similar to the o
