ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peterrei...@apache.org
Subject cvs commit: ant/proposal/xdocs/src/org/apache/tools/ant/taskdefs SubAnt.xml
Date Tue, 09 Dec 2003 16:28:50 GMT
peterreilly    2003/12/09 08:28:50

  Modified:    proposal/xdocs/src/org/apache/tools/ant/taskdefs SubAnt.xml
  Log:
  remove 'crs from SubAnt.xml
  
  Revision  Changes    Path
  1.6       +69 -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.6
  diff -u -r1.5 -r1.6
  --- SubAnt.xml	22 May 2003 07:27:51 -0000	1.5
  +++ SubAnt.xml	9 Dec 2003 16:28:50 -0000	1.6
  @@ -1,70 +1,70 @@
  -<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>
  -        &lt;project name="subant" default="subant1"&gt;
  -        &lt;property name="build.dir" value="subant.build"/&gt;
  -        &lt;target name="subant1"&gt;
  -            &lt;subant target=""&gt;
  -              &lt;property name="build.dir" value="subant1.build"/&gt;
  -              &lt;property name="not.overloaded" value="not.overloaded"/&gt;
  -              &lt;fileset dir="." includes="*/build.xml"/&gt;
  -            &lt;/subant&gt;
  -        &lt;/target&gt;
  -        &lt;/project&gt;
  -        </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>
  -          &lt;subant target=""&gt;
  -             &lt;propertyset&gt;
  -                  &lt;propertyref prefix="toplevel"/&gt;
  -                  &lt;mapper type="glob" from="foo*" to="bar*"/&gt;
  -             &lt;/propertyset&gt;
  -             &lt;fileset dir="." includes="*/build.xml"/&gt;
  -          &lt;/subant&gt;
  -        </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 &quot;foo&quot; are passed, their
names are changed to start with &quot;bar&quot; instead
  -        </p>
  -        <pre>
  -          &lt;subant target="compile" genericantfile="/opt/project/build1.xml"&gt;
  -             &lt;dirset dir="." includes="projects*"/&gt;
  -          &lt;/subant&gt;
  -        </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>
  +            <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>
  +        &lt;project name="subant" default="subant1"&gt;
  +        &lt;property name="build.dir" value="subant.build"/&gt;
  +        &lt;target name="subant1"&gt;
  +            &lt;subant target=""&gt;
  +              &lt;property name="build.dir" value="subant1.build"/&gt;
  +              &lt;property name="not.overloaded" value="not.overloaded"/&gt;
  +              &lt;fileset dir="." includes="*/build.xml"/&gt;
  +            &lt;/subant&gt;
  +        &lt;/target&gt;
  +        &lt;/project&gt;
  +        </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>
  +          &lt;subant target=""&gt;
  +             &lt;propertyset&gt;
  +                  &lt;propertyref prefix="toplevel"/&gt;
  +                  &lt;mapper type="glob" from="foo*" to="bar*"/&gt;
  +             &lt;/propertyset&gt;
  +             &lt;fileset dir="." includes="*/build.xml"/&gt;
  +          &lt;/subant&gt;
  +        </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 &quot;foo&quot; are passed, their
names are changed to start with &quot;bar&quot; instead
  +        </p>
  +        <pre>
  +          &lt;subant target="compile" genericantfile="/opt/project/build1.xml"&gt;
  +             &lt;dirset dir="." includes="projects*"/&gt;
  +          &lt;/subant&gt;
  +        </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: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message