Author: bodewig
Date: Thu Aug 28 08:06:17 2008
New Revision: 689846
URL: http://svn.apache.org/viewvc?rev=689846&view=rev
Log:
to be honest, there is yet another twist to basedir
Modified:
ant/core/trunk/docs/manual/CoreTasks/ant.html
Modified: ant/core/trunk/docs/manual/CoreTasks/ant.html
URL:
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTasks/ant.html?rev=689846&r1=689845&r2=689846&view=diff
==============================================================================
--- ant/core/trunk/docs/manual/CoreTasks/ant.html (original)
+++ ant/core/trunk/docs/manual/CoreTasks/ant.html Thu Aug 28 08:06:17 2008
@@ -80,11 +80,14 @@
</tr>
<tr>
<td valign="top">dir</td>
- <td valign="top">the directory to use as a basedir for the new Ant
project.
+ <td valign="top">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.</td>
+ setting of the called project.<br/>
+ Also serves as the directory to resolve the antfile and output
+ attribute's values (if any).
+ </td>
<td valign="top" align="center">No</td>
</tr>
<tr>
@@ -275,6 +278,14 @@
<p>If you add even deeper levels of nesting, things get even more
complicated and you need to apply the above table recursively.</p>
+<p>If the basedir of the outer most build has been specified as a
+ property on the command line (i.e. <code>-Dbasedir=some-value</code>
+ or a <code>-propertyfile</code> argument) the value provided will
+ get an even higher priority. For any <code><ant></code> 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.</p>
+
<h3>Examples</h3>
<blockquote><pre>
<ant antfile="subproject/subbuild.xml"
target="compile"/>