peterreilly 2003/12/12 02:52:19
Modified: docs/manual/CoreTasks Tag: ANT_16_BRANCH subant.html
proposal/xdocs/src/org/apache/tools/ant/taskdefs Tag:
ANT_16_BRANCH SubAnt.xml
Log:
Sync with HEAD
Revision Changes Path
No revision
No revision
1.7.2.4 +27 -53 ant/docs/manual/CoreTasks/subant.html
Index: subant.html
===================================================================
RCS file: /home/cvs/ant/docs/manual/CoreTasks/subant.html,v
retrieving revision 1.7.2.3
retrieving revision 1.7.2.4
diff -u -r1.7.2.3 -r1.7.2.4
--- subant.html 24 Oct 2003 09:00:29 -0000 1.7.2.3
+++ subant.html 12 Dec 2003 10:52:18 -0000 1.7.2.4
@@ -19,6 +19,7 @@
<td valign="bottom">
<font size="+3" face="arial,helvetica,sanserif"><strong>Subant
Task</strong></font>
+ <br><font face="arial,helvetica,sanserif">Calls a given target
for all defined sub-builds.</font>
</td>
<td>
<!-- PROJECT LOGO -->
@@ -47,13 +48,13 @@
<tr><td><blockquote>
<p>
- Calls a given target for all defined sub-builds. This is an extension
- of ant for bulk project execution.
-
- <strong>This task must no be used outside of a
- <code>target</code> if it invokes the same build file it is
- part of.</strong>
-
+ Calls a given target for all defined sub-builds.
+ This is an extension
+ of ant for bulk project execution.
+
+ <strong>This task must no be used outside of a
+ <code>target</code> if it invokes the same build file it is
+ part of.</strong>
</p>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<!-- Subsection heading -->
@@ -74,7 +75,7 @@
with different base directories, use the genericantfile
attribute
</li>
<li>if you want to run <code>directory1/mybuild.xml</code>,
<code>directory2/mybuild.xml</code>, <code>....</code>,
- use the antfile attribute. The subant task does not set
the base directory for you in this case.<br/> because you
can specify it in each build file.
+ use the antfile attribute. The subant task does not set
the base directory for you in this case, because you can specify it in each
build file.
</li>
</ul>
@@ -86,6 +87,10 @@
</table>
<!-- End Description -->
+ <!-- Ignore -->
+
+
+
<!-- Start Attributes -->
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td> </td></tr>
@@ -252,10 +257,8 @@
</td></tr>
<tr><td><blockquote>
Adds a directory set to the implicit build path. <p> <em>Note that
the directories will be added to the build path in no particular order, so if
order is significant, one should use a file list instead!</em>
-<short-description><![CDATA[Adds a directory set to the implicit build
path.]]></short-description>
-<description>
- <![CDATA[Adds a directory set to the implicit build path. <p>
<em>Note that the directories will be added to the build path in no particular
order, so if order is significant, one should use a file list instead!</em>]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -269,10 +272,8 @@
</td></tr>
<tr><td><blockquote>
Adds an ordered file list to the implicit build path. <p> <em>Note
that contrary to file and directory sets, file lists can reference non-existent
files or directories!</em>
-<short-description><![CDATA[Adds an ordered file list to the implicit build
path.]]></short-description>
-<description>
- <![CDATA[Adds an ordered file list to the implicit build path.
<p> <em>Note that contrary to file and directory sets, file lists can reference
non-existent files or directories!</em>]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -286,10 +287,8 @@
</td></tr>
<tr><td><blockquote>
Adds a file set to the implicit build path. <p> <em>Note that the
directories will be added to the build path in no particular order, so if order
is significant, one should use a file list instead!</em>
-<short-description><![CDATA[Adds a file set to the implicit build
path.]]></short-description>
-<description>
- <![CDATA[Adds a file set to the implicit]]><![CDATA[ build path.
<p> <em>Note that the directories will be added to the build path in no
particular order, so if order is significant, one should use a file list
instead!</em>]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -303,10 +302,8 @@
</td></tr>
<tr><td><blockquote>
Corresponds to <code><ant></code>'s nested
<code><property></code> element.
-<short-description><![CDATA[Corresponds to <code><ant></code>'s nested
<code><property></code> element.]]></short-description>
-<description>
- <![CDATA[Corresponds to <code><ant></code>'s nested
<code><property></code> element.]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -320,27 +317,8 @@
</td></tr>
<tr><td><blockquote>
Corresponds to <code><ant></code>'s nested
<code><propertyset></code> element.
-<short-description><![CDATA[Corresponds to <code><ant></code>'s nested
<code><propertyset></code> element.]]></short-description>
-<description>
- <![CDATA[Corresponds to <code><ant></code>'s nested
<code><propertyset></code> element.]]>
- </description>
-
- </blockquote></td></tr>
- </table>
- <!-- End Element -->
- <!-- Start Element -->
- <table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td> </td></tr>
- <tr><td bgcolor="#828DA6">
- <font color="#ffffff" face="arial,helvetica.sanserif" size="-1">
- <strong>reference</strong>
(org.apache.tools.ant.taskdefs.Ant.Reference)</font>
- </td></tr>
- <tr><td><blockquote>
- Corresponds to <code><ant></code>'s nested
<code><reference></code> element.
-<short-description><![CDATA[Corresponds to <code><ant></code>'s nested
<code><reference></code> element.]]></short-description>
-<description>
- <![CDATA[Corresponds to <code><ant></code>'s nested
<code><reference></code> element.]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -354,10 +332,8 @@
</td></tr>
<tr><td><blockquote>
Creates a nested build path, and add it to the implicit build path.
-<short-description><![CDATA[Creates a nested build path, and add it to the
implicit build path.]]></short-description>
-<description>
- <![CDATA[Creates a nested build path, and add it to the implicit
build path.]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
@@ -371,10 +347,8 @@
</td></tr>
<tr><td><blockquote>
Creates a nested <code><buildpathelement></code>, and add it
to the implicit build path.
-<short-description><![CDATA[Creates a nested
<code><buildpathelement></code>, and add it to the implicit build
path.]]></short-description>
-<description>
- <![CDATA[Creates a nested <code><buildpathelement></code>,
and add it to the implicit build path.]]>
- </description>
+ <!-- Ignore -->
+ <!-- Ignore -->
</blockquote></td></tr>
</table>
No revision
No revision
1.5.2.1 +70 -69
ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs/SubAnt.xml
Index: SubAnt.xml
===================================================================
RCS file:
/home/cvs/ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs/SubAnt.xml,v
retrieving revision 1.5
retrieving revision 1.5.2.1
diff -u -r1.5 -r1.5.2.1
--- SubAnt.xml 22 May 2003 07:27:51 -0000 1.5
+++ SubAnt.xml 12 Dec 2003 10:52:18 -0000 1.5.2.1
@@ -1,70 +1,71 @@
-<external>
- <description>
- <p>
- <i>EXPERIMENTAL:</i> This task is experimental and may be under
continual
- change till Ant1.6 ships; it may even be omitted from the
product.
- </p>
- <p>
- Calls a given target for all defined sub-builds. This is an extension
- of ant for bulk project execution.
- </p>
- <subsection name="Use with directories">
- <p>
- subant can be used with directory sets to execute a build
from different directories.
- 2 different options are offered :
- </p>
- <ul>
- <li>
- to run the same build file
<code>/somepath/otherpath/mybuild.xml</code>
- with different base directories, use the genericantfile
attribute
- </li>
- <li>if you want to run <code>directory1/mybuild.xml</code>,
<code>directory2/mybuild.xml</code>, <code>....</code>,
- use the antfile attribute. The subant task does not set
the base directory for you in this case.<br/> because you
can specify it in each build file.
- </li>
- </ul>
- </subsection>
- </description>
- <section anchor="examples" name="Examples">
- <pre>
- <project name="subant" default="subant1">
- <property name="build.dir" value="subant.build"/>
- <target name="subant1">
- <subant target="">
- <property name="build.dir" value="subant1.build"/>
- <property name="not.overloaded" value="not.overloaded"/>
- <fileset dir="." includes="*/build.xml"/>
- </subant>
- </target>
- </project>
- </pre>
- <p>
- this snippet build file will run ant in each subdirectory of the
project directory,
- where a file called build.xml can be found.
- The property build.dir will have the value subant1.build in the
ant projects called by subant.
- </p>
- <pre>
- <subant target="">
- <propertyset>
- <propertyref prefix="toplevel"/>
- <mapper type="glob" from="foo*" to="bar*"/>
- </propertyset>
- <fileset dir="." includes="*/build.xml"/>
- </subant>
- </pre>
- <p>
- this snippet build file will run ant in each subdirectory of the
project directory,
- where a file called build.xml can be found.
- All properties whose name starts with "foo" are
passed, their names are changed to start with "bar" instead
- </p>
- <pre>
- <subant target="compile"
genericantfile="/opt/project/build1.xml">
- <dirset dir="." includes="projects*"/>
- </subant>
- </pre>
- <p>
- assuming the subdirs of the project dir are called projects1,
projects2, projects3
- this snippet will execute the compile target of
/opt/project/build1.xml,
- setting the basedir to projects1, projects2, projects3
- </p>
- </section>
+<external>
+ <description>
+ <p>
+ Calls a given target for all defined sub-builds.
+ This is an extension
+ of ant for bulk project execution.
+
+ <strong>This task must no be used outside of a
+ <code>target</code> if it invokes the same build file it is
+ part of.</strong>
+ </p>
+ <subsection name="Use with directories">
+ <p>
+ subant can be used with directory sets to execute a build
from different directories.
+ 2 different options are offered :
+ </p>
+ <ul>
+ <li>
+ to run the same build file
<code>/somepath/otherpath/mybuild.xml</code>
+ with different base directories, use the genericantfile
attribute
+ </li>
+ <li>if you want to run <code>directory1/mybuild.xml</code>,
<code>directory2/mybuild.xml</code>, <code>....</code>,
+ use the antfile attribute. The subant task does not set
the base directory for you in this case, because you can specify it in each
build file.
+ </li>
+ </ul>
+ </subsection>
+ </description>
+ <section anchor="examples" name="Examples">
+ <pre>
+ <project name="subant" default="subant1">
+ <property name="build.dir" value="subant.build"/>
+ <target name="subant1">
+ <subant target="">
+ <property name="build.dir" value="subant1.build"/>
+ <property name="not.overloaded" value="not.overloaded"/>
+ <fileset dir="." includes="*/build.xml"/>
+ </subant>
+ </target>
+ </project>
+ </pre>
+ <p>
+ this snippet build file will run ant in each subdirectory of the
project directory,
+ where a file called build.xml can be found.
+ The property build.dir will have the value subant1.build in the
ant projects called by subant.
+ </p>
+ <pre>
+ <subant target="">
+ <propertyset>
+ <propertyref prefix="toplevel"/>
+ <mapper type="glob" from="foo*" to="bar*"/>
+ </propertyset>
+ <fileset dir="." includes="*/build.xml"/>
+ </subant>
+ </pre>
+ <p>
+ this snippet build file will run ant in each subdirectory of the
project directory,
+ where a file called build.xml can be found.
+ All properties whose name starts with "foo" are
passed, their names are changed to start with "bar" instead
+ </p>
+ <pre>
+ <subant target="compile"
genericantfile="/opt/project/build1.xml">
+ <dirset dir="." includes="projects*"/>
+ </subant>
+ </pre>
+ <p>
+ assuming the subdirs of the project dir are called projects1,
projects2, projects3
+ this snippet will execute the compile target of
/opt/project/build1.xml,
+ setting the basedir to projects1, projects2, projects3
+ </p>
+ </section>
</external>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
