From 46520b1e01c0197f09f8dadfa4db060972cff13d Mon Sep 17 00:00:00 2001 From: Stefan Bodewig Date: Thu, 28 Aug 2008 15:06:17 +0000 Subject: [PATCH] to be honest, there is yet another twist to basedir git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@689846 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/ant.html | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/docs/manual/CoreTasks/ant.html b/docs/manual/CoreTasks/ant.html index 50e7eb589..72c51bbb9 100644 --- a/docs/manual/CoreTasks/ant.html +++ b/docs/manual/CoreTasks/ant.html @@ -80,11 +80,14 @@ inside of targets.

dir - the directory to use as a basedir for the new Ant project. + the directory to use as a basedir for the new Ant project. Defaults to the current project's basedir, unless inheritall has been set to false, in which case it doesn't have a default value. This will override the basedir - setting of the called project. + setting of the called project.
+ Also serves as the directory to resolve the antfile and output + attribute's values (if any). + No @@ -275,6 +278,14 @@ targets so specified, in the order specified.

If you add even deeper levels of nesting, things get even more complicated and you need to apply the above table recursively.

+

If the basedir of the outer most build has been specified as a + property on the command line (i.e. -Dbasedir=some-value + or a -propertyfile argument) the value provided will + get an even higher priority. For any <ant> task + that doesn't specify a dir attribute, the new project's basedir will + be the value specified on the command line - no matter how deeply + nested into layers of build files the task may be.

+

Examples

 <ant antfile="subproject/subbuild.xml" target="compile"/>