From 9c616cacdee86e1cf0c5d98b57b62f8ee178a0a8 Mon Sep 17 00:00:00 2001 From: Stefan Bodewig Date: Wed, 16 Jul 2008 15:56:12 +0000 Subject: [PATCH] more on relative paths to executables git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@677317 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/exec.html | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/docs/manual/CoreTasks/exec.html b/docs/manual/CoreTasks/exec.html index 0df73287f..91e9c65bb 100644 --- a/docs/manual/CoreTasks/exec.html +++ b/docs/manual/CoreTasks/exec.html @@ -35,7 +35,18 @@ to send input to it is via the input and inputstring attributes. Also note that since 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.

- +

If you want to execute an executable using a path relative to the + project's basedir, you may need to + use vmlauncher="false" on some operating systems - but + even this may fail (Solaris 8/9 has been reported as problematic). + The resolveexecutable attribute should be more + reliable, as would be something like +

+  <property name="executable-full-path"
+            location="../relative/path/to/executable"/>
+  <exec executable="${executable-full-path}" ...
+
+

Windows Users

The <exec> task delegates to Runtime.exec which in turn