Kedziora, Rebecca wrote:
Ah... the " worked!
Some places I don't have problems with the spaces in the dir name like
when using the move task, but using it in a redirection of the exec
task caused me grief.
The reason for this is that the move task is handled internally by NAnt,
but the re
:
nant-users@lists.sourceforge.net
Subject: RE: [Nant-users] Exec
program can't handle dir name with spaces
Ah... the "
worked!
Some places I don't have
problems with the spaces in the dir name like when using the move task, but
using it in a redirection of the exec
lto:[EMAIL PROTECTED] On Behalf Of Robert
SchneiderSent: Thursday, November 03, 2005 10:08 AMTo:
nant-users@lists.sourceforge.netSubject: RE: [Nant-users] Exec
program can't handle dir name with spaces
Try to use quotes.
Hope this helps.
"${buildlog.dir}\${source.
Title: Exec program can't handle dir name with spaces
Try to use quotes. Hope
this helps.
"${buildlog.dir}\${source.changes.log.filename}"
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kedziora, Rebecca
Sent: Thursday, November 03, 2005
4:55 PM
To:
nant
Title: Exec program can't handle dir name with spaces
I’m not sure if this will work, but
attempt to surround the last portion of your commandline attribute with “"”
I haven’t tried this myself, but I
think it should solve your problems…
Example:
RE: [Nant-users] Exec program can't handle dir name with spaces
Title: Exec program can't handle dir name with spaces
This is a command line
issue. You're essentially
executing:
C:\>changes.cmd root
branch tstamp > c:\builds\smc management center\logfiles\filename
So it's not
reading the whole path for the pipe, just the "c:\builds\smc", and
then
