stevel 2004/11/05 00:58:10 Modified: docs/manual/CoreTasks exec.html Log: PR: 32066: exec favours .exe over . com. Yes, it does. Revision Changes Path 1.42 +12 -0 ant/docs/manual/CoreTasks/exec.html Index: exec.html =================================================================== RCS file: /home/cvs/ant/docs/manual/CoreTasks/exec.html,v retrieving revision 1.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- exec.html 10 Sep 2004 15:16:11 -0000 1.41 +++ exec.html 5 Nov 2004 08:58:09 -0000 1.42 @@ -18,6 +18,18 @@ in Ant 1.6, any attempt to read input in the forked program will receive an EOF (-1). This is a change from Ant 1.5, where such an attempt would block.</p> + + +<h4>Windows Users</h4> +<p>The <exec> task delegates to <code>Runtime.exec</code> which in turn +apparently calls <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/createprocess.asp"> +<code>::CreateProcess</code></a>. It is the latter Win32 function that defines +the exact semantics of the call. In particular, if you do not put a file extension +on the executable, only ".EXE" files are looked for, not ".COM", ".CMD" or other file +types listed in the environment variable PATHEXT. That is only used by the shell. + +</p> + <h4>Cygwin Users</h4> <p>In general the <exec> task will not understand paths such as /bin/sh for the executable parameter. This is because the Java VM in which Ant is running is a
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]