From e4160c6fe5be9b3c4b843f403576771d1d218d75 Mon Sep 17 00:00:00 2001 From: Steve Loughran Date: Fri, 5 Nov 2004 08:58:09 +0000 Subject: [PATCH] PR: 32066: exec favours .exe over . com. Yes, it does. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276993 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/exec.html | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/manual/CoreTasks/exec.html b/docs/manual/CoreTasks/exec.html index 1a5da5d70..f08be7609 100644 --- a/docs/manual/CoreTasks/exec.html +++ b/docs/manual/CoreTasks/exec.html @@ -18,6 +18,18 @@ to send input to it is via the input and inputstring attributes. Also note that 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.

+ + +

Windows Users

+

The <exec> task delegates to Runtime.exec which in turn +apparently calls +::CreateProcess. 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. + +

+

Cygwin Users

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