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 redirection is being handled by your .cmd script. Try executing
the command directly from a DOS command line, and you'll see that it has
the same problem. In fact, if you had used some other program directly,
instead of the .cmd script which fires up the Windows command processor,
it wouldn't work at all - because programs generally leave the
redirection handling to that processor.
In the long run, you're better off using the 'output=...' attribute of
the exec task, which makes the intent much clearer and will work with
any program, not just .cmd/.bat/etc. This attribute will currently tee
the output into both the given file and the NAnt log, but there's at
least one open bug report and two proposed solutions for fixing this. I
also suggest shifting to using the <arg> mechanism instead of the
commandline= attribute, because it will also avoid gotchas such as this.
Gary
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
