consistent use of <code> - submitted by Larry Shatzer

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@277057 13f79535-47bb-0310-9956-ffa450edef68
20 years ago · 3935a662f5
--- a/+ 1
+++ b/+ 1
@@ -112,6 +112,7 @@ Kevin Ross
 Kevin Z Grey
 Kirk Wylie
 Kyle Adams
 Larry Shatzer
 Larry Streepy
 Les Hughes
 Levi Cook
--- a/docs/manual/CoreTasks/ant.html
+++ b/docs/manual/CoreTasks/ant.html
@@ -33,14 +33,14 @@ by using nested property tags. These properties are always passed
 to the new project and any project created in that project
 regardless of the setting of <i>inheritAll</i>.  This allows you to
 parameterize your subprojects.  Properties defined on the command line
 can not be overridden by nested &lt;property&gt; elements.</p>
 can not be overridden by nested <code>&lt;property&gt;</code> elements.</p>

 <p>References to data types can also be passed to the new project, but
 by default they are not.  If you set the inheritrefs attribute to
 true, all references will be copied, but they will not override
 references defined in the new project.</p>

 <p>Nested <a href="#reference"><i>&lt;reference&gt;</i></a> elements
 <p>Nested <a href="#reference"><i><code>&lt;reference&gt;</code></i></a> elements
 can also be used to copy references from the calling project to the
 new project, optionally under a different id.  References taken from
 nested elements will override existing references that have been
@@ -105,7 +105,7 @@ inside of targets.</p>
 task</a>. <br/>
 These properties become equivalent to properties you define on
 the command line. These are special properties and they will always get passed
 down, even through additional &lt;*ant*&gt; tasks with inheritall set to
 down, even through additional <code>&lt;*ant*&gt;</code> tasks with inheritall set to
 false (see above). <br/>
 Note that the <code>refid</code> attribute points to a
 reference in the calling project, not in the new one.</p>
@@ -142,7 +142,7 @@ href="../CoreTypes/propertyset.html">propertyset</a>s.</p>

 <h4>target</h4>

 <p>You can specify multiple targets using nested &lt;target&gt; elements
 <p>You can specify multiple targets using nested <code>&lt;target&gt;</code> elements
 instead of using the target attribute.  These will be executed as if
 Ant had been invoked with a single target whose dependencies are the
 targets so specified, in the order specified.</p>
@@ -186,12 +186,12 @@ details:</p>
    <td valign="top">omitted</td>
    <td valign="top">true</td>
    <td valign="top">basedir of calling project (the one whose build
        file contains the &lt;ant&gt; task).</td>
        file contains the <code>&lt;ant&gt;</code> task).</td>
  </tr>
  <tr>
    <td valign="top">omitted</td>
    <td valign="top">false</td>
    <td valign="top">basedir attribute of the &lt;project&gt; element
    <td valign="top">basedir attribute of the <code>&lt;project&gt;</code> element
        of the new project</td>
  </tr>
 </table>
--- a/docs/manual/CoreTasks/antcall.html
+++ b/docs/manual/CoreTasks/antcall.html
@@ -26,9 +26,9 @@ by using nested param tags. These properties are always passed
 to the new project and any project created in that project
 regardless of the setting of <i>inheritAll</i>.  This allows you to
 parameterize your subprojects.  Properties defined on the command line
 can not be overridden by nested &lt;param&gt; elements.</p>
 can not be overridden by nested <code>&lt;param&gt;</code> elements.</p>

 <p>Nested <a href="#reference"><i>&lt;reference&gt;</i></a> elements can
 <p>Nested <a href="#reference"><i><code>&lt;reference&gt</code>;</i></a> elements can
 be used to copy references from the calling project to the new
 project, optionally under a different id.  References taken from
 nested elements will override existing references that have been
@@ -91,7 +91,7 @@ attribute).</p>
 href="property.html">property</a> for usage guidelines.<br/>
 These properties become equivalent to properties you define on
 the command line. These are special properties and they will always get passed
 down, even through additional &lt;*ant*&gt; tasks with inheritall set to
 down, even through additional <code>&lt;*ant*&gt;</code> tasks with inheritall set to
 false (see above).
 </p>

@@ -127,7 +127,7 @@ href="../CoreTypes/propertyset.html">propertyset</a>s.</p>

 <h4>target</h4>

 <p>You can specify multiple targets using nested &lt;target&gt; elements
 <p>You can specify multiple targets using nested <code>&lt;target&gt;</code> elements
 instead of using the target attribute.  These will be executed as if
 Ant had been invoked with a single target whose dependencies are the
 targets so specified, in the order specified.</p>
--- a/docs/manual/CoreTasks/apply.html
+++ b/docs/manual/CoreTasks/apply.html
@@ -46,7 +46,7 @@ to send input to it is via the input and inputstring attributes.</p>
  </tr>
  <tr>
    <td valign="top">dest</td>
    <td valign="top">the directory where the &lt;apply&gt; expects the target files will be placed by the 
    <td valign="top">the directory where the <code>&lt;apply&gt;</code> expects the target files will be placed by the 
                     command, when it is executed. 
    </td>
    <td align="center" valign="top">Yes, if you specify a nested mapper</td>
@@ -360,24 +360,24 @@ the <code>.o</code> and SOURCEFILE with the absolute name of the
 <blockquote><pre>
 &lt;mapper id=&quot;out&quot; type=&quot;glob&quot;
           from=&quot;src${file.separator}*.file&quot;
           to=&quot;dest${file.separator}*.out&quot; /&gt;
           to=&quot;dest${file.separator}*.out&quot;/&gt;

 &lt;apply executable=&quot;processfile&quot; dest=&quot;dest&quot;&gt;
  &lt;fileset dir=&quot;src&quot; includes=&quot;*.file&quot;/&gt;
  &lt;mapper refid=&quot;out&quot; /&gt;
  &lt;mapper refid=&quot;out&quot;/&gt;
  &lt;redirector&gt;
    &lt;outputmapper refid=&quot;out&quot; /&gt;
    &lt;outputmapper refid=&quot;out&quot;/&gt;
  &lt;/redirector&gt;
 &lt;/apply&gt;
 </pre></blockquote>
 Applies the fictitious &quot;processfile&quot; executable to all
 files matching <code>*.file</code> in the <CODE>src</CODE> directory.
 The <CODE>out</CODE> &lt;mapper&gt; has been set up to map
 <CODE>*.file</CODE> to <CODE>*.out</CODE>, then this &lt;mapper&gt;
 The <CODE>out</CODE> <code>&lt;mapper&gt;</code> has been set up to map
 <CODE>*.file</CODE> to <CODE>*.out</CODE>, then this <code>&lt;mapper&gt;</code>
 is used to specify <CODE>targetfile</CODE>s for this &lt;apply&gt;
 task.  A reference to <CODE>out</CODE> is then used as an
 &lt;outputmapper&gt; nested in a &lt;redirector&gt;, which in turn is
 nested beneath this &lt;apply&gt; instance.  This allows us to perform
 <code>&lt;outputmapper&gt;</code> nested in a <code>&lt;redirector&gt;</code>, which in turn is
 nested beneath this <code>&lt;apply&gt;</code> instance.  This allows us to perform
 dependency checking against output files--the target files in this case.

 <hr><p align="center">Copyright &copy; 2000-2004 The Apache Software Foundation. All rights
--- a/docs/manual/CoreTasks/apt.html
+++ b/docs/manual/CoreTasks/apt.html
@@ -23,13 +23,13 @@
  <tr>
    <td valign="top">compile</td>
    <td valign="top">After running the Apt, should the code be compiled.  (see the
                     "-nocompile" flag on the Apt executable)</td>
                     <code>-nocompile</code> flag on the Apt executable)</td>
    <td align="center" valign="top">No, defaults to false.</td>
  </tr>
  <tr>
    <td valign="top">factory</td>
    <td valign="top">The fully qualified classname of the AnnotationProcessFactory to be used
                     to construct annotation processors.  This represents the "-factory"
                     to construct annotation processors.  This represents the <code>-factory</code>
                     command line flag of the Apt executable.</td>
    <td align="center" valign="top">No</td>
  </tr>
@@ -37,13 +37,13 @@
    <td valign="top">factorypathref</td>
    <td valign="top">The reference id of the path used to find the classes needed by the
                     AnnotationProcessorFactory (and the location of the factory itself).
                     This represents the "-factorypath" flag on the Apt executable.</td>
                     This represents the <code>-factorypath</code> flag on the Apt executable.</td>
    <td align="center" valign="top">No</td>
  </tr>
  <tr>
    <td valign="top">preprocessdir</td>
    <td valign="top">The directory used for preprocessing.  This is the directory where the
                     generated source code will be place.  This represents the "-s" flag on
                     generated source code will be place.  This represents the <code>-s</code> flag on
                     the Apt executable.</td>
    <td align="center" valign="top">No</td>
  </tr>
@@ -56,13 +56,13 @@

 <p>You can specify the path used to find the classes needed by the AnnotationProcessorFactory
   at runtime, using this element.  It is represents as a generic path like structure.  This
   represents the "-factorypath" flag on the Apt executable.</p>
   represents the <code>-factorypath</code> flag on the Apt executable.</p>


 <h4>option</h4>

 <p>Used to represent a generic option to pass to Apt.  This represents the "-A" flag on the
   Apt executable.  You can specify zero or more &lt;option&gt; elements.</p>
 <p>Used to represent a generic option to pass to Apt.  This represents the <code>-A</code> flag on the
   Apt executable.  You can specify zero or more <code>&lt;option&gt;</code> elements.</p>

 <table border="1" cellpadding="2" cellspacing="0">
 <tbody><tr>
@@ -128,19 +128,19 @@ The "compiler" attribute is ignored, as it is forced to use the Apt compiler
    &lt;javac srcdir="${src}"
         destdir="${build}"
         classpath="xyz.jar"
         debug="on" /&gt;
         debug="on"/&gt;

    &lt;javac srcdir="${preprocess.dir}"
         destdir="${build}"
         classpath="xyz.jar"
         debug="true" /&gt;
         debug="true"/&gt;
 </pre>

 This may involve more build file coding, but the speedup gained from switching
 to jikes may justify the effort.
 <p>
 </p><hr>
 <p align="center">Copyright © 2004 The Apache Software Foundation.
 <p align="center">Copyright &copy; 2004 The Apache Software Foundation.
 All rights Reserved.</p>

 </body></html>
--- a/docs/manual/CoreTasks/changelog.html
+++ b/docs/manual/CoreTasks/changelog.html
@@ -12,7 +12,7 @@
 <p>Generates an XML-formatted report file of the change logs recorded in a
 <a href="http://www.cvshome.org/" target="_top">CVS</a> repository. </p>
 <p><b>Important:</b> This task needs "cvs" on the path. If it isn't, you will get
 an error (such as error 2 on windows). If &lt;cvs&gt; doesn't work, try to execute cvs.exe
 an error (such as error 2 on windows). If <code>&lt;cvs&gt;</code> doesn't work, try to execute cvs.exe
 from the command line in the target directory in which you are working.
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
@@ -48,7 +48,7 @@ from the command line in the target directory in which you are working.
  <tr>
    <td valign="top">passfile</td>
    <td valign="top">Password file to read passwords from.</td>
    <td align="center" valign="top">No, default file ~/.cvspass.</td>
    <td align="center" valign="top">No, default file <code>~/.cvspass</code>.</td>
  </tr>
  <tr>
    <td valign="top">failonerror</td>
@@ -184,7 +184,7 @@ It writes these changes into the file <code>changelog.xml</code>.</p>
 <p>Generates a change log report on the <code>ANT_16_BRANCH</code>.</p>
 <pre>
 &lt;cvschangelog dir=&quot;c:/dev/asf/ant.head&quot; passfile=&quot;c:/home/myself/.cvspass&quot;
                destfile=&quot;changelogant.xml&quot; tag=&quot;ANT_16_BRANCH&quot; /&gt;
                destfile=&quot;changelogant.xml&quot; tag=&quot;ANT_16_BRANCH&quot;/&gt;
 </pre>
 <h4>Generate Report</h4>
 <p>Ant includes a basic XSLT stylesheet that you can use to generate 
--- a/docs/manual/CoreTasks/copy.html
+++ b/docs/manual/CoreTasks/copy.html
@@ -162,9 +162,9 @@ tokens in files that are copied.
 FilterChain</a>s.</p>

 <p>
 If &lt;filterset&gt; and &lt;filterchain&gt; elements are used inside the
 same &lt;copy&gt; task, all &lt;filterchain&gt; elements are processed first
 followed by &lt;filterset&gt; elements.
 If <code>&lt;filterset&gt;</code> and <code>&lt;filterchain&gt;</code> elements are used inside the
 same <code>&lt;copy&gt;</code> task, all <code>&lt;filterchain&gt;</code> elements are processed first
 followed by <code>&lt;filterset&gt;</code> elements.
 </p>

 <h3>Examples</h3>
--- a/docs/manual/CoreTasks/cvspass.html
+++ b/docs/manual/CoreTasks/cvspass.html
@@ -30,7 +30,7 @@
  <tr>
    <td valign="top">passfile</td>
    <td valign="top">Password file to add the entry to.</td>
    <td align="center" valign="top">No, default is ~/.cvspass.</td>
    <td align="center" valign="top">No, default is <code>~/.cvspass</code>.</td>
  </tr>
 </table>
 <h3>Examples</h3>
@@ -40,7 +40,7 @@
 <p>Adds an entry into the ~/.cvspass password file.</p>

 <hr>
 <p align="center">Copyright &copy; 2001,2003 Apache Software Foundation. All rights
 <p align="center">Copyright &copy; 2001,2003-2004 Apache Software Foundation. All rights
 Reserved.</p>
 </body>
 </html>
--- a/docs/manual/CoreTasks/cvstagdiff.html
+++ b/docs/manual/CoreTasks/cvstagdiff.html
@@ -9,7 +9,7 @@
 <p>Generates an XML-formatted report file of the changes between two tags or dates recorded in a
 <a href="http://www.cvshome.org/" target="_top">CVS</a> repository. </p>
 <p><b>Important:</b> This task needs "cvs" on the path. If it isn't, you will get
 an error (such as error 2 on windows). If &lt;cvs&gt; doesn't work, try to execute cvs.exe
 an error (such as error 2 on windows). If <code>&lt;cvs&gt;</code> doesn't work, try to execute <code>cvs.exe</code>
 from the command line in the target directory in which you are working.
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
@@ -92,7 +92,7 @@ from the command line in the target directory in which you are working.
  <tr>
    <td valign="top">passfile</td>
    <td valign="top">Password file to read passwords from.</td>
    <td align="center" valign="top">No, default file ~/.cvspass.</td>
    <td align="center" valign="top">No, default file <code>~/.cvspass</code>.</td>
  </tr>
  <tr>
    <td valign="top">failonerror</td>
--- a/docs/manual/CoreTasks/dependset.html
+++ b/docs/manual/CoreTasks/dependset.html
@@ -34,7 +34,7 @@ FileList, all target files will be removed.
 </p>
 <p>
 DependSet is useful to capture dependencies that are not or cannot be
 determined algorithmically.  For example, the &lt;style&gt; task only
 determined algorithmically.  For example, the <code>&lt;style&gt;</code> task only
 compares the source XML file and XSLT stylesheet against the target
 file to determined whether to restyle the source.  Using dependset you
 can extend this dependency checking to include a DTD or XSD file as
--- a/docs/manual/CoreTasks/exec.html
+++ b/docs/manual/CoreTasks/exec.html
@@ -1,4 +1,4 @@
 <html>
 html>

 <head>
 <meta http-equiv="Content-Language" content="en-us">
@@ -21,7 +21,7 @@ EOF (-1). This is a change from Ant 1.5, where such an attempt would block.</p>


 <h4>Windows Users</h4>
 <p>The &lt;exec&gt; task delegates to <code>Runtime.exec</code> which in turn
 <p>The <code>&lt;exec&gt;</code> task delegates to <code>Runtime.exec</code> which in turn
 apparently calls <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/createprocess.asp">
 <code>::CreateProcess</code></a>. It is the latter Win32 function that defines
 the exact semantics of the call. In particular, if you do not put a file extension
@@ -31,7 +31,7 @@ types listed in the environment variable PATHEXT. That is only used by the shell
 </p>

 <h4>Cygwin Users</h4>
 <p>In general the &lt;exec&gt; task will not understand paths such as /bin/sh for
 <p>In general the <code>&lt;exec&gt;</code> task will not understand paths such as /bin/sh for
 the executable parameter. This is because the Java VM in which Ant is running is a
 Windows executable and is not aware of Cygwin conventions.
 </p>
@@ -299,14 +299,14 @@ will fall back to the task level attributes.  In practice this means that
 defaults can be specified for input, output, and error output files.
 </p>
 <h3>Errors and return codes</h3>
 By default the return code of a &lt;exec&gt; is ignored; when you set
 By default the return code of a <code>&lt;exec&gt;</code> is ignored; when you set
 <code>failonerror="true"</code> then any return code signaling failure
 (OS specific) causes the build to fail. Alternatively, you can set
 <code>resultproperty</code> to the name of a property and have it assigned to
 the result code (barring immutability, of course).
 <p>
 If the attempt to start the program fails with an OS dependent error code,
 then &lt;exec&gt; halts the build unless <code>failifexecutionfails</code>
 then <code>&lt;exec&gt;</code> halts the build unless <code>failifexecutionfails</code>
 is set to <code>false</code>. You can use that to run a program if it exists, but
 otherwise do nothing.
 <p>
@@ -349,10 +349,10 @@ ant process. The browser will let be open.</p>
                errorproperty=&quot;redirector.err&quot;
                inputstring=&quot;blah before blah&quot;&gt;
        &lt;inputfilterchain&gt;
            &lt;replacestring from=&quot;before&quot; to=&quot;after&quot; /&gt;
            &lt;replacestring from=&quot;before&quot; to=&quot;after&quot;/&gt;
        &lt;/inputfilterchain&gt;
        &lt;outputmapper type=&quot;merge&quot; to=&quot;redirector.out&quot; /&gt;
        &lt;errormapper type=&quot;merge&quot; to=&quot;redirector.err&quot; /&gt;
        &lt;outputmapper type=&quot;merge&quot; to=&quot;redirector.out&quot;/&gt;
        &lt;errormapper type=&quot;merge&quot; to=&quot;redirector.err&quot;/&gt;
    &lt;/redirector&gt;
 &lt;/exec&gt;
 </pre></blockquote>
--- a/docs/manual/CoreTasks/fail.html
+++ b/docs/manual/CoreTasks/fail.html
@@ -49,7 +49,7 @@ or character data nested into the element.</p>

 <p>As an alternative to the <i>if</i>/<i>unless</i> attributes,
  conditional failure can be achieved using a single nested
  &lt;condition&gt; element, which should contain exactly one
  <code>&lt;condition&gt;</code> element, which should contain exactly one
  core or custom condition.  For information about conditions, see
  <a href="conditions.html">here</a>.<br /><b>Since Ant 1.6.2</b>
 </p>
--- a/docs/manual/CoreTasks/import.html
+++ b/docs/manual/CoreTasks/import.html
@@ -136,13 +136,13 @@ project).</p>
 </table>

 <h3>Examples</h3>
 <pre>&nbsp; &lt;import file=&quot;../common-targets.xml&quot; /&gt;
 <pre>&nbsp; &lt;import file=&quot;../common-targets.xml&quot;/&gt;
 </pre>

 <p>Imports targets from the common-targets.xml file that is in a parent
 directory.</p>

 <pre>&nbsp; &lt;import file=&quot;${deploy-platform}.xml&quot; /&gt;
 <pre>&nbsp; &lt;import file=&quot;${deploy-platform}.xml&quot;/&gt;
 </pre>

 <p>Imports the project defined by the property deploy-platform</p>
--- a/docs/manual/CoreTasks/java.html
+++ b/docs/manual/CoreTasks/java.html
@@ -268,7 +268,7 @@ will fall back to the task level attributes.  In practice this means that
 defaults can be specified for input, output, and error output files.
 </p>
 <h3>Errors and return codes</h3>
 By default the return code of a &lt;java&gt; is ignored. Alternatively, you can set <code>resultproperty</code> to the name
 By default the return code of a <code>&lt;java&gt;</code> is ignored. Alternatively, you can set <code>resultproperty</code> to the name
 of a property and have it assigned to the result code (barring immutability,
 of course).
 When you set <code>failonerror="true"</code>, the only possible value for <code>resultproperty</code> is 0. Any non zero response is treated as an
@@ -313,7 +313,7 @@ and with a maximum memory of 128MB. Any non zero return code breaks the build.
 </pre>
 <strong>Note</strong>: you can not specify the (highly deprecated) MSJVM, "jview.exe" as the
 JVM, as it takes different parameters for other JVMs,
 That JVM can be started from &lt;exec&gt; if required.
 That JVM can be started from <code>&lt;exec&gt;</code> if required.
 <hr>
 <p align="center">Copyright &copy; 2000-2004 The Apache Software Foundation. All rights
 Reserved.</p>
--- a/docs/manual/CoreTasks/javac.html
+++ b/docs/manual/CoreTasks/javac.html
@@ -511,8 +511,8 @@ javac's default searching mechanism then you can unset the sourcepath
 attribute:
 <pre>  &lt;javac sourcepath=&quot;&quot; srcdir=&quot;${src}&quot;
         destdir=&quot;${build}&quot; &gt;
    &lt;include name="**/*.java" /&gt;
    &lt;exclude name="**/Example.java" /&gt;
    &lt;include name="**/*.java"/&gt;
    &lt;exclude name="**/Example.java"/&gt;
  &lt;/javac&gt;</pre>
 That way the javac will compile all java source files under &quot;${src}&quot;
 directory but skip the examples. The compiler will even produce errors if some of
--- a/docs/manual/CoreTasks/javadoc.html
+++ b/docs/manual/CoreTasks/javadoc.html
@@ -254,8 +254,8 @@ means any VM of at least version 1.2.</p>
  </tr>
  <tr>
    <td valign="top">linkoffline</td>
    <td valign="top">Link to docs at &lt;url&gt; using package list at
    &lt;url2&gt; - separate the URLs by using a space character -- see
    <td valign="top">Link to docs at <code>&lt;url&gt;</code> using package list at
    <code>&lt;url2&gt;</code> - separate the URLs by using a space character -- see
    also the nested <code>link</code> element.</td>
    <td align="center" valign="top">1.2+</td>
    <td align="center" valign="top">No</td>
@@ -694,7 +694,7 @@ only available with Java 1.4.</p>
    <td valign="top">path</td>
    <td valign="top">A path specifying the search path for the taglet class
            (e.g. <code>/home/taglets</code>).
            The path may also be specified by a nested &lt;path&gt; element</td>
            The path may also be specified by a nested <code>&lt;path&gt;</code> element</td>
    <td align="center" valign="top">No</td>
  </tr>
 </table>
@@ -724,7 +724,7 @@ arguments</a>. <em>Since Ant 1.6</em></p>
           windowtitle=&quot;Test API&quot;&gt;
    &lt;doctitle&gt;&lt;![CDATA[&lt;h1&gt;Test&lt;/h1&gt;]]&gt;&lt;/doctitle&gt;
    &lt;bottom&gt;&lt;![CDATA[&lt;i&gt;Copyright &amp;#169; 2000 Dummy Corp. All Rights Reserved.&lt;/i&gt;]]&gt;&lt;/bottom&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot; /&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot;/&gt;
    &lt;group title=&quot;Group 1 Packages&quot; packages=&quot;com.dummy.test.a*&quot;/&gt;
    &lt;group title=&quot;Group 2 Packages&quot; packages=&quot;com.dummy.test.b*:com.dummy.test.c*&quot;/&gt;
    &lt;link offline=&quot;true&quot; href=&quot;http://java.sun.com/products/jdk/1.2/docs/api/&quot; packagelistLoc=&quot;C:\tmp&quot;/&gt;
@@ -741,13 +741,13 @@ arguments</a>. <em>Since Ant 1.6</em></p>
           windowtitle=&quot;Test API&quot;&gt;

    &lt;packageset dir=&quot;src&quot; defaultexcludes=&quot;yes&quot;&gt;
      &lt;include name=&quot;com/dummy/test/**&quot; /&gt;
      &lt;include name=&quot;com/dummy/test/**&quot;/&gt;
      &lt;exclude name=&quot;com/dummy/test/doc-files/**&quot;/&gt;
    &lt;/packageset&gt;

    &lt;doctitle&gt;&lt;![CDATA[&lt;h1&gt;Test&lt;/h1&gt;]]&gt;&lt;/doctitle&gt;
    &lt;bottom&gt;&lt;![CDATA[&lt;i&gt;Copyright &amp;#169; 2000 Dummy Corp. All Rights Reserved.&lt;/i&gt;]]&gt;&lt;/bottom&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot; /&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot;/&gt;
    &lt;group title=&quot;Group 1 Packages&quot; packages=&quot;com.dummy.test.a*&quot;/&gt;
    &lt;group title=&quot;Group 2 Packages&quot; packages=&quot;com.dummy.test.b*:com.dummy.test.c*&quot;/&gt;
    &lt;link offline=&quot;true&quot; href=&quot;http://java.sun.com/products/jdk/1.2/docs/api/&quot; packagelistLoc=&quot;C:\tmp&quot;/&gt;
@@ -764,13 +764,13 @@ arguments</a>. <em>Since Ant 1.6</em></p>
           windowtitle=&quot;Test API&quot;&gt;

    &lt;fileset dir=&quot;src&quot; defaultexcludes=&quot;yes&quot;&gt;
      &lt;include name=&quot;com/dummy/test/**&quot; /&gt;
      &lt;include name=&quot;com/dummy/test/**&quot;/&gt;
      &lt;exclude name=&quot;com/dummy/test/doc-files/**&quot;/&gt;
    &lt;/fileset&gt;

    &lt;doctitle&gt;&lt;![CDATA[&lt;h1&gt;Test&lt;/h1&gt;]]&gt;&lt;/doctitle&gt;
    &lt;bottom&gt;&lt;![CDATA[&lt;i&gt;Copyright &amp;#169; 2000 Dummy Corp. All Rights Reserved.&lt;/i&gt;]]&gt;&lt;/bottom&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot; /&gt;
    &lt;tag name=&quot;todo&quot; scope=&quot;all&quot; description=&quot;To do:&quot;/&gt;
    &lt;group title=&quot;Group 1 Packages&quot; packages=&quot;com.dummy.test.a*&quot;/&gt;
    &lt;group title=&quot;Group 2 Packages&quot; packages=&quot;com.dummy.test.b*:com.dummy.test.c*&quot;/&gt;
    &lt;link offline=&quot;true&quot; href=&quot;http://java.sun.com/products/jdk/1.2/docs/api/&quot; packagelistLoc=&quot;C:\tmp&quot;/&gt;
--- a/docs/manual/CoreTasks/loadproperties.html
+++ b/docs/manual/CoreTasks/loadproperties.html
@@ -10,8 +10,8 @@
 <h3>Description</h3>
 <p>
 Load a file's contents as Ant properties.  This is equivalent
 to &lt;property file|resource=&quot;...&quot;/&gt; except that it
 supports nested &lt;filterchain&gt; elements.
 to <code>&lt;property file|resource=&quot;...&quot;/&gt;</code> except that it
 supports nested <code>&lt;filterchain&gt;</code> elements.
 </p>

 <p>If you want to simulate <a href="property.html">property</a>'s
@@ -49,7 +49,7 @@ filter.</p>
    <td valign="top">classpathref</td>
    <td valign="top">the classpath to use when looking up a resource,
      given as <a href="../using.html#references">reference</a>
      to a &lt;path&gt; defined elsewhere..</td>
      to a <code>&lt;path&gt;</code> defined elsewhere..</td>
    <td align="center" valign="top">No</td>
  </tr>
 </table>
--- a/docs/manual/CoreTasks/macrodef.html
+++ b/docs/manual/CoreTasks/macrodef.html
@@ -16,10 +16,10 @@
    <h2><a name="macrodef">MacroDef</a></h2>
    <h3>Description</h3>
    <p>
      This defines a new task using a &lt;sequential&gt;
      nested task as a template. Nested elements &lt;attribute&gt; and
      &lt;element&gt; are used to specify attributes and elements of
      the new task. These get substituted into the  &lt;sequential&gt;
      This defines a new task using a <code>&lt;sequential&gt;</code>
      nested task as a template. Nested elements <code>&lt;attribute&gt;</code> and
      <code>&lt;element&gt;</code> are used to specify attributes and elements of
      the new task. These get substituted into the <code>&lt;sequential&gt;</code>
      task when the new task is run.
    </p>
    <h3>Note</h3>
@@ -225,10 +225,10 @@
 </pre>
    </blockquote>
    <p>
      The following fragment defines a task called &lt;call-cc&gt; which
      The following fragment defines a task called <code>&lt;call-cc&gt;</code> which
      take the attributes "target", "link" and "target.dir" and the
      nested element "cc-elements". The body of the task
      uses the &lt;cc&gt; task from the
      uses the <code>&lt;cc&gt;</code> task from the
      <a href="http://ant-contrib.sourceforge.net/">ant-contrib</a> project.
    </p>
    <blockquote>
--- a/docs/manual/CoreTasks/mail.html
+++ b/docs/manual/CoreTasks/mail.html
@@ -250,7 +250,7 @@ will be replaced with the <code>buildname</code> property's value.</p>

 &lt;mail mailhost=&quot;somehost@xyz.com&quot; mailport=&quot;25&quot; subject=&quot;Test build&quot;  charset=&quot;utf-8&quot;&gt;
  &lt;from address=&quot;me@myist.com&quot;/&gt;
  &lt;to address=&quot;all@xyz.com&quot; /&gt;
  &lt;to address=&quot;all@xyz.com&quot;/&gt;
  &lt;message&gt;some international text:${line2}&lt;/message&gt;
 &lt;/mail&gt;
 </pre></blockquote>
--- a/docs/manual/CoreTasks/move.html
+++ b/docs/manual/CoreTasks/move.html
@@ -139,9 +139,9 @@ href="../CoreTypes/mapper.html#identity-mapper">identity</a>.</p>
 FilterChain</a>s.</p>

 <p>
 If &lt;filterset&gt; and &lt;filterchain&gt; elements are used inside the
 same &lt;move&gt; task, all &lt;filterchain&gt; elements are processed first
 followed by &lt;filterset&gt; elements.
 If <code>&lt;filterset&gt;</code> and <code>&lt;filterchain&gt;</code> elements are used inside the
 same <code>&lt;move&gt;</code> task, all <code>&lt;filterchain&gt;</code> elements are processed first
 followed by <code>&lt;filterset&gt;</code> elements.
 </p>

 <h3>Examples</h3>
@@ -161,7 +161,7 @@ followed by &lt;filterset&gt; elements.
 </pre>
  <i>or, since Ant 1.6.3:</i>
 <pre>
  &lt;move file=&quot;src/dir&quot; tofile=&quot;new/dir/to/move/to&quot; /&gt;
  &lt;move file=&quot;src/dir&quot; tofile=&quot;new/dir/to/move/to&quot;/&gt;
 </pre>
 <p><b>Move a set of files to a new directory</b></p>
 <pre>
--- a/docs/manual/CoreTasks/nice.html
+++ b/docs/manual/CoreTasks/nice.html
@@ -35,12 +35,12 @@
  </tr>
 </table>
 <h3>Examples</h3>
 <pre>   &lt;nice newpriority=&quot;10&quot; /&gt;</pre>
 <pre>   &lt;nice newpriority=&quot;10&quot;/&gt;</pre>
 Set the Thread priority to 10.
 <pre>   &lt;nice currentpriority=&quot;priority&quot; /&gt;</pre>
 <pre>   &lt;nice currentpriority=&quot;priority&quot;/&gt;</pre>
 Store the current Thread priority in the user property "priority".
 <pre>
   &lt;nice currentpriority=&quot;currentpriority&quot; newpriority=&quot;1&quot; /&gt;
   &lt;nice currentpriority=&quot;currentpriority&quot; newpriority=&quot;1&quot;/&gt;
 </pre>
 <p>Set the current Thread priority to 1, storing the original
 priority in the user property "currentpriority".  This
--- a/docs/manual/CoreTasks/parallel.html
+++ b/docs/manual/CoreTasks/parallel.html
@@ -59,7 +59,7 @@ threads do not interact. For example, two javac compile tasks which write
 classes into the same destination directory may interact where one tries to
 read a class for dependency information while the other task is writing the
 class file. Be sure to avoid these types of interactions within a
 &lt;parallel&gt; task</p>
 <code>&lt;parallel&gt;</code> task</p>

 <p>Any valid Ant task may be embedded within a
 parallel task, including other parallel tasks.</p>
@@ -71,7 +71,7 @@ flag is set, the parallel task will complete without waiting for other nested
 tasks to complete in other threads.
 </p>

 <p>If any of the tasks within the &lt;parallel&gt; task fails and failonany is
 <p>If any of the tasks within the <code>&lt;parallel&gt;</code> task fails and failonany is
 not set, the remaining tasks in other threads will continue to run until
 all threads have completed. In this situation, the parallel task will also fail.</p>

@@ -104,7 +104,7 @@ semantics and is best used for "embarassingly parallel" tasks.</p>

 <h4>daemons</h4>
 <p>
 The parallel task supports a &lt;daemons&gt; nested element. This is a list of tasks
 The parallel task supports a <code>&lt;daemons&gt;</code> nested element. This is a list of tasks
 which are to be run in parallel daemon threads. The parallel task will not wait for
 these tasks to complete. Being daemon threads, however, they will not prevent Ant from
 completing, whereupon the threads are terminated. Failures in daemon threads which
@@ -114,7 +114,7 @@ reported.
 </p>

 <p>Daemon tasks can be used, for example, to start test servers which might not be easily
 terminated from Ant. By using &lt;daemons&gt; such servers do not halt the build.
 terminated from Ant. By using <code>&lt;daemons&gt;</code> such servers do not halt the build.
 </p>


--- a/docs/manual/CoreTasks/presetdef.html
+++ b/docs/manual/CoreTasks/presetdef.html
@@ -49,7 +49,7 @@
    </table>
    <h3>Parameters specified as nested elements</h3>
    <h4>another type with attributes or elements set</h4>
    <p>The &lt;presetdef&gt; task takes one nested element as a parameter.
    <p>The <code>&lt;presetdef&gt;</code> task takes one nested element as a parameter.
      This nested element can be any other type or task. The attributes
      and elements that need to be preset are placed here.
    </p>
@@ -146,7 +146,7 @@ called:
 </pre>
     </blockquote>
    <hr></hr>
    <p align="center">Copyright &copy; 2003 Apache Software
    <p align="center">Copyright &copy; 2003-2004 Apache Software
      Foundation. All rights Reserved.</p>
    
  </body>
--- a/docs/manual/CoreTasks/property.html
+++ b/docs/manual/CoreTasks/property.html
@@ -119,7 +119,7 @@ SYSTEM).
  <tr>
    <td valign="top">classpathref</td>
    <td valign="top">the classpath to use when looking up a resource,
      given as <a href="../using.html#references">reference</a> to a &lt;path&gt; defined
      given as <a href="../using.html#references">reference</a> to a <code>&lt;path&gt;</code> defined
      elsewhere..</td>
    <td align="center" valign="top">No</td>
  </tr>
--- a/docs/manual/CoreTasks/style.html
+++ b/docs/manual/CoreTasks/style.html
@@ -28,11 +28,11 @@ inclusion/exclusion of files works, and how to write patterns.</p>
  attributes of <code>&lt;fileset&gt;</code> (<code>dir</code> becomes <code>basedir</code>)
  as well as the nested <code>&lt;include&gt;</code>, <code>&lt;exclude&gt;</code>
  and <code>&lt;patternset&gt;</code> elements.</p>
 <p>This task supports the use of a nested &lt;param&gt; element which is used to pass values
  to an &lt;xsl:param&gt; declaration.</p>
 <p>This task supports the use of a nested <code>&lt;param&gt;</code> element which is used to pass values
  to an <code>&lt;xsl:param&gt;</code> declaration.</p>
 <p>This task supports the use of a nested <a href="../CoreTypes/xmlcatalog.html">xmlcatalog</a>
 element which is used to perform Entity and URI resolution</p>
 <p><i>&lt;style&gt; and &lt;xslt&gt; refer to the same Ant task and can be used interchangeably.</i></p>
 <p><i><code>&lt;style&gt;</code> and <code>&lt;xslt&gt;</code> refer to the same Ant task and can be used interchangeably.</i></p>
 <p>If you want to use Xalan-J 1 or XSL:P, you also need Ant's optional.jar</p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
@@ -57,7 +57,7 @@ element which is used to perform Entity and URI resolution</p>
    <td valign="top">extension</td>
    <td valign="top">desired file extension to be used for the targets. If not
      specified, the default is &quot;.html&quot;.  Will be ignored if
      a nested &lt;mapper&gt; has been specified.</td>
      a nested <code>&lt;mapper&gt;</code> has been specified.</td>
    <td align="center" valign="top">No</td>
  </tr>
  <tr>
--- a/docs/manual/CoreTasks/subant.html
+++ b/docs/manual/CoreTasks/subant.html
@@ -491,7 +491,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2004, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/CoreTasks/tempfile.html
+++ b/docs/manual/CoreTasks/tempfile.html
@@ -46,7 +46,7 @@
      </td></tr>

      <tr><td><blockquote>
        This task sets a property to the name of a temporary file. Unlike the Java1.2 method to create a temporary file, this task does work on Java1.1. Also, it does not actually create the temporary file, but it does guarantee that the file did not exist when the task was executed. <p> Examples <pre>&lt;tempfile property="temp.file" /&gt;</pre> create a temporary file <pre>&lt;tempfile property="temp.file" suffix=".xml" /&gt;</pre> create a temporary file with the .xml suffix. <pre>&lt;tempfile property="temp.file" destDir="build"/&gt;</pre> create a temp file in the build subdir
        This task sets a property to the name of a temporary file. Unlike the Java1.2 method to create a temporary file, this task does work on Java1.1. Also, it does not actually create the temporary file, but it does guarantee that the file did not exist when the task was executed. <p> Examples <pre>&lt;tempfile property="temp.file"/&gt;</pre> create a temporary file <pre>&lt;tempfile property="temp.file" suffix=".xml"/&gt;</pre> create a temporary file with the .xml suffix. <pre>&lt;tempfile property="temp.file" destDir="build"/&gt;</pre> create a temp file in the build subdir
      </blockquote></td></tr>

    </table>
@@ -178,7 +178,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/CoreTasks/tstamp.html
+++ b/docs/manual/CoreTasks/tstamp.html
@@ -15,7 +15,7 @@ properties in the current project. By default,
 the <code>DSTAMP</code> property is in the
 format &quot;yyyyMMdd&quot;, <code>TSTAMP</code> is in the
 format &quot;hhmm&quot;, and <code>TODAY</code> is in the
 format &quot;MMMM dd yyyy&quot;. Use the nested &lt;format&gt; element
 format &quot;MMMM dd yyyy&quot;. Use the nested <code>&lt;format&gt;</code> element
 to specify a different format.</p>

 <p>These properties can be used in the build-file, for instance, to create
@@ -128,7 +128,7 @@ using English locale (eg. 21-May-2001).</p>
 </pre>
 <p>
 Creates a timestamp, in the property touch.time, 5 hours before the current time. The format in this example
 is suitable for use with the &lt;touch&gt; task. The standard properties are set also.</p>
 is suitable for use with the <code>&lt;touch&gt;</code> task. The standard properties are set also.</p>

 <pre>
  &lt;tstamp prefix="start"/&gt;
--- a/docs/manual/CoreTasks/uptodate.html
+++ b/docs/manual/CoreTasks/uptodate.html
@@ -119,10 +119,10 @@ if <code>/usr/local/bin/testit</code> is newer than
  </p>
  <pre>
    &lt;uptodate property="checkUptodate.uptodate"&gt;
      &lt;srcfiles dir="src" includes="*" /&gt;
      &lt;srcfiles dir="src" includes="*"/&gt;
      &lt;mapper type="merge" to="../dest/output.done"/&gt;
    &lt;/uptodate&gt;
    &lt;echo message="checkUptodate result: ${checkUptodate.uptodate}" /&gt;
    &lt;echo message="checkUptodate result: ${checkUptodate.uptodate}"/&gt;
  </pre>
  <p>
    The previous example can be a bit confusing, so it may be better to
@@ -131,7 +131,7 @@ if <code>/usr/local/bin/testit</code> is newer than
  <pre>
    &lt;property name="dest.dir" location="dest"/&gt;
    &lt;uptodate property="checkUptodate.uptodate"&gt;
      &lt;srcfiles dir="src" includes="*" /&gt;
      &lt;srcfiles dir="src" includes="*"/&gt;
      &lt;mapper type="merge" to="${dest.dir}/output.done"/&gt;
    &lt;/uptodate&gt;
  </pre>
--- a/docs/manual/CoreTasks/whichresource.html
+++ b/docs/manual/CoreTasks/whichresource.html
@@ -198,7 +198,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/CoreTasks/xmlproperty.html
+++ b/docs/manual/CoreTasks/xmlproperty.html
@@ -153,7 +153,7 @@ element is used to perform entity resolution.</p>

 <h5>default loading</h5>
 <p>This entry in a build file:
 <pre>   &lt;xmlproperty file="somefile.xml" /&gt;</pre>
 <pre>   &lt;xmlproperty file="somefile.xml"/&gt;</pre>
 is equivalent to the following properties:
 <pre>
   root-tag(myattr)=true
--- a/docs/manual/CoreTasks/zip.html
+++ b/docs/manual/CoreTasks/zip.html
@@ -59,7 +59,7 @@ filenames contain non US-ASCII characters. Use the encoding attribute
 and set it to UTF8 to create zip files that can safely be read by
 Java.</p>

 <p>Starting with Ant 1.5.2, &lt;zip&gt; can store Unix permissions
 <p>Starting with Ant 1.5.2, <code>&lt;zip&gt;</code> can store Unix permissions
 inside the archive (see description of the filemode and dirmode
 attributes for <a href="../CoreTypes/zipfileset.html">&lt;zipfileset&gt;</a>).
 Unfortunately there is no portable way to store these permissions.
--- a/docs/manual/CoreTypes/antlib.html
+++ b/docs/manual/CoreTypes/antlib.html
@@ -41,7 +41,7 @@
      </pre>
    </blockquote>
    <p>
      The other attributes of &lt;typedef&gt; may be used as well.
      The other attributes of <code>&lt;typedef&gt;</code> may be used as well.
      For example, assuming that the <i>sample.xml</i> is in a jar
      file <i>sample.jar</i> also containing the classes, the
      following build fragment will define the <i>if</i> and <i>scriptpathmapper</i>
@@ -115,12 +115,12 @@
    <p>
      Definitions defined in antlibs may be used in antlibs. However
      the namespace that definitions are placed in are dependent on
      the &lt;typedef&gt; that uses the antlib. To deal with this
      the <code>&lt;typedef&gt;</code> that uses the antlib. To deal with this
      problem, the definitions are placed in the namepace URI <i>ant:current</i>
      for the duration of the antlib execution.
      For example the following antlib defines the task &lt;if&gt;, the
      type &lt;isallowed&gt; and a macro
      &lt;ifallowed&gt; that makes use of the task and type:
      For example the following antlib defines the task <code>&lt;if&gt;</code>, the
      type <code>&lt;isallowed&gt;</code> and a macro
      <code>&lt;ifallowed&gt;</code> that makes use of the task and type:
    </p>
    <blockquote>
      <pre>
@@ -148,7 +148,7 @@
    </p>
    <p>
      As the names defined in the antlib are in the namespace uri as
      specified by the calling &lt;typedef&gt; or by automatic element
      specified by the calling <code>&lt;typedef&gt;</code> or by automatic element
      resolution, one may reuse names from core ant types and tasks,
      provided the caller uses a namespace uri. For example, the
      following antlib may be used to define defaults for various
--- a/docs/manual/CoreTypes/assertions.html
+++ b/docs/manual/CoreTypes/assertions.html
@@ -11,8 +11,8 @@
 <p>
 The <tt>assertions</tt> type enables or disables the Java 1.4 assertions feature,
 on a whole Java program, or components of a program. It can be used
 in <a href="../CoreTasks/java.html">&lt;java&gt;</a> and
 <a href="../OptionalTasks/junit.html">&lt;junit&gt;</a> to add extra validation to code.  
 in <a href="../CoreTasks/java.html"><code>&lt;java&gt;</code></a> and
 <a href="../OptionalTasks/junit.html"><code>&lt;junit&gt;</code></a> to add extra validation to code.  

 <p>
 Assertions are covered in the 
--- a/docs/manual/CoreTypes/custom-programming.html
+++ b/docs/manual/CoreTypes/custom-programming.html
@@ -231,7 +231,7 @@ public class MatchNumberSelectors extends BaseSelectorContainer {
      This method is still supported for backward compatibility.
    </p>
    <p>You can write your own selectors and use them within the selector
      containers by specifying them within the &lt;custom&gt; tag.</p>
      containers by specifying them within the <code>&lt;custom&gt;</code> tag.</p>

        <p>To create a new Custom Selector, you have to create a class that
        implements
--- a/docs/manual/CoreTypes/filterchain.html
+++ b/docs/manual/CoreTypes/filterchain.html
@@ -16,8 +16,8 @@ to a file 'bar' - you would do something like<P>
 cat foo|head -n10|grep blee &gt; bar
 </code><P>
 Ant was not flexible enough.  There was no way for the
 &lt;copy&gt; task to do something similar.  If you wanted
 the &lt;copy&gt; task to get the first 10 lines, you would have
 <code>&lt;copy&gt;</code> task to do something similar.  If you wanted
 the <code>&lt;copy&gt;</code> task to get the first 10 lines, you would have
 had to create special attributes:<P>
 <code>
 &lt;copy file=&quot;foo&quot; tofile=&quot;bar&quot; head=&quot;10&quot; contains=&quot;blee&quot;/&gt;
@@ -37,7 +37,7 @@ tasks to support FilterChains.  A FilterChain is a group of
 ordered FilterReaders.  Users can define their own FilterReaders
 by just extending the java.io.FilterReader class.  Such custom
 FilterReaders can be easily plugged in as nested elements of
 &lt;filterchain&gt; by using &lt;filterreader&gt; elements.
 <code>&lt;filterchain&gt;</code> by using <code>&lt;filterreader&gt;</code> elements.
 <P>
 Example:
 <BLOCKQUOTE><PRE>
@@ -79,7 +79,7 @@ is equivalent to:
 &lt;/loadfile&gt;
 </PRE></BLOCKQUOTE>

 The following built-in tasks support nested &lt;filterchain&gt; elements.<BR>
 The following built-in tasks support nested <code>&lt;filterchain&gt;</code> elements.<BR>
 <a href="../CoreTasks/concat.html">Concat</a>,<BR>
 <a href="../CoreTasks/copy.html">Copy</a>,<BR>
 <a href="../CoreTasks/loadfile.html">LoadFile</a>,<BR>
@@ -135,8 +135,8 @@ org.apache.tools.type.Parameterizable.

 <P>
 <H4>Nested Elements:</H4>
 &lt;filterreader&gt; supports &lt;classpath&gt; and &lt;param&gt;
 as nested elements.  Each &lt;param&gt; element may take in the following
 <code>&lt;filterreader&gt;</code> supports <code>&lt;classpath&gt;</code> and <code>&lt;param&gt;</code>
 as nested elements.  Each <code>&lt;param&gt;</code> element may take in the following
 attributes - name, type and value.
 <P>
 The following FilterReaders are supplied with the default
@@ -209,7 +209,7 @@ This results in the property modifiedmessage holding the value
  message=&quot;All these moments will be lost in time, like teardrops in the ${weather}&quot;
  file=&quot;loadfile1.tmp&quot;
  /&gt;
 &lt;property name=&quot;weather&quot; value=&quot;rain&quot; /&gt;
 &lt;property name=&quot;weather&quot; value=&quot;rain&quot;/&gt;
 &lt;loadfile property=&quot;modifiedmessage&quot; srcFile=&quot;loadfile1.tmp&quot;&gt;
  &lt;filterchain&gt;
    &lt;filterreader classname=&quot;org.apache.tools.ant.filters.ExpandProperties&quot;/&gt;
@@ -223,7 +223,7 @@ Convenience method:
  message=&quot;All these moments will be lost in time, like teardrops in the ${weather}&quot;
  file=&quot;loadfile1.tmp&quot;
  /&gt;
 &lt;property name=&quot;weather&quot; value=&quot;rain&quot; /&gt;
 &lt;property name=&quot;weather&quot; value=&quot;rain&quot;/&gt;
 &lt;loadfile property=&quot;modifiedmessage&quot; srcFile=&quot;loadfile1.tmp&quot;&gt;
  &lt;filterchain&gt;
    &lt;expandproperties/&gt;
@@ -1308,7 +1308,7 @@ Custom string filters and tokenizers may be plugged in by
 extending the interfaces org.apache.tools.ant.filters.TokenFilter.Filter
 and org.apache.tools.ant.util.Tokenizer respectly.

 They are defined the build file using &lt;typedef/&gt;. For
 They are defined the build file using <code>&lt;typedef/&gt;</code>. For
 example a string filter that capitalizes words may be declared as:
 <blockquote><pre>
 package my.customant;
--- a/docs/manual/CoreTypes/mapper.html
+++ b/docs/manual/CoreTypes/mapper.html
@@ -93,7 +93,7 @@ implicitly configured as a <a href="#composite-mapper">composite mapper</a>.
 <b>Examples:</b>
 <blockquote><pre>
 &lt;mapper type=&quot;identity&quot;/&gt;
 &lt;identitymapper /&gt;
 &lt;identitymapper/&gt;
 </pre></blockquote>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
@@ -124,7 +124,7 @@ leading directory information stripped off. Both <code>to</code> and
 <b>Examples:</b>
 <blockquote><pre>
 &lt;mapper type=&quot;flatten&quot;/&gt;
 &lt;flattenmapper /&gt;
 &lt;flattenmapper/&gt;
 </pre></blockquote>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
@@ -444,7 +444,7 @@ with <code>&lt;uptodate&gt;</code> and <code>&lt;junit&gt;</code> output.</p>
 <b>Examples:</b>
 <blockquote><pre>
 &lt;compositemapper&gt;
  &lt;identitymapper /&gt;
  &lt;identitymapper/&gt;
  &lt;packagemapper from="*.java" to="*"/&gt;
 &lt;/compositemapper&gt;
 </pre></blockquote>
@@ -473,7 +473,7 @@ with <code>&lt;uptodate&gt;</code> and <code>&lt;junit&gt;</code> output.</p>
 <b>Examples:</b>
 <blockquote><pre>
 &lt;chainedmapper&gt;
  &lt;flattenmapper /&gt;
  &lt;flattenmapper/&gt;
  &lt;globmapper from="*" to="new/path/*"/&gt;
  &lt;mapper&gt;
    &lt;globmapper from="*" to="*1"/&gt;
--- a/docs/manual/CoreTypes/namespace.html
+++ b/docs/manual/CoreTypes/namespace.html
@@ -17,7 +17,7 @@
        prefixes in tag names a special meaning, and thus build files using
        colons in user-defined tasks and types will break.
      </li>
      <li> Attributes with the names 'xmlns' and 'xmlns:&lt;prefix&gt;'
      <li> Attributes with the names 'xmlns' and 'xmlns:<code>&lt;prefix&gt;</code>'
        are not treated specially, which means that custom tasks and types have
        actually been able to use such attributes as parameter names. Again,
        such tasks/types are going to break when namespace support is enabled
@@ -34,15 +34,15 @@
      easy to get into name conflicts. When individual types are defined, the
      build file writer can do some name-spacing manually (for example, using
      "tomcat-deploy" instead of just "deploy"). But when defining whole
      libraries of types using the &lt;typedef&gt; 'resource' attribute, the
      libraries of types using the <code>&lt;typedef&gt;</code> 'resource' attribute, the
      build file writer has no chance to override or even prefix the names
      supplied by the library. </p>
    <h2>Assigning Namespaces</h2>

    <p>
      Adding a 'prefix' attribute to &lt;typedef&gt; might have been enough,
      Adding a 'prefix' attribute to <code>&lt;typedef&gt;</code> might have been enough,
      but XML already has a well-known method for name-spacing. Thus, instead
      of adding a 'prefix' attribute, the &lt;typedef&gt; and &lt;taskdef&gt;
      of adding a 'prefix' attribute, the <code>&lt;typedef&gt;</code> and <code>&lt;taskdef&gt;</code>
      tasks get a 'uri' attribute, which stores the URI of the XML namespace
      with which the type should be associated:
    </p><pre> &lt;typedef resource="org/example/tasks.properties" uri="<a href="http://example.org/tasks">http://example.org/tasks</a>"/&gt;
@@ -73,7 +73,7 @@
 &lt;/project&gt;
 </pre>
    <p>
      Here, the namespace is set as the default namespace for the &lt;task&gt;
      Here, the namespace is set as the default namespace for the <code>&lt;task&gt;</code>
      element and all its descendants.
    </p>
    <h2>Default namespace</h2>
@@ -171,9 +171,9 @@
      Ant types and tasks are now free to accept arbritrary named types as
      nested elements, as long as the concrete type implements the interface
      expected by the task/type. The most obvioius example for this is the
      &lt;condition&gt; task, which supports various nested conditions, all
      <code>&lt;condition&gt;</code> task, which supports various nested conditions, all
      of which extend the interface <tt>Condition</tt>. To integrate a
      custom condition in Ant, you can now simply &lt;typedef&gt; the
      custom condition in Ant, you can now simply <code>&lt;typedef&gt;</code> the
      condition, and then use it anywhere develop.html#nestedtypwhere conditions are allowed
      (assuming the containing element has a generic <tt>add(Condition)</tt> or <tt>addConfigured(Configured)</tt>method):
 </p><pre> &lt;typedef resource="org/example/conditions.properties" uri="<a href="http://example.org/conditions">http://example.org/conditions</a>"/&gt;
--- a/docs/manual/CoreTypes/patternset.html
+++ b/docs/manual/CoreTypes/patternset.html
@@ -124,7 +124,7 @@ by tasks that support this feature, or by FileSets.</p>
 <p>Note that while the <code>includes</code> and
 <code>excludes</code> attributes accept
 multiple elements separated by commas or spaces, the nested
 &lt;include&gt; and &lt;exclude&gt; elements expect their name
 <code>&lt;include&gt;</code> and <code>&lt;exclude&gt;</code> elements expect their name
 attribute to hold a single pattern.</p>
 <p>The nested elements allow you to use if and unless arguments to
 specify that the element should only be used if a property is set, or
--- a/docs/manual/CoreTypes/permissions.html
+++ b/docs/manual/CoreTypes/permissions.html
@@ -120,7 +120,7 @@ A permissions set implictly contains the following permissions:
 &lt;grant class=&quot;java.util.PropertyPermission&quot; name=&quot;java.vm.vendor&quot; actions=&quot;read&quot;&gt;
 &lt;grant class=&quot;java.util.PropertyPermission&quot; name=&quot;java.vm.name&quot; actions=&quot;read&quot;&gt;
 </blockquote></pre>
 These permissions can be revoked via &lt;revoke&gt; elements if necessary.
 These permissions can be revoked via <code>&lt;revoke&gt;</code> elements if necessary.

 <h3>Examples</h3>
 <blockquote><pre>
--- a/docs/manual/CoreTypes/redirector.html
+++ b/docs/manual/CoreTypes/redirector.html
@@ -14,7 +14,7 @@ task, used to execute an external process, stands as a very
 basic example.  The executed process may accept input, produce
 output, or do either or both depending upon various circumstances.
 Output may be classified as &quot;output&quot; or as &quot;error
 output.&quot;  The &lt;redirector&gt; type provides a concrete means
 output.&quot;  The <code>&lt;redirector&gt;</code> type provides a concrete means
 of redirecting input and output featuring the use of
 <a href="./mapper.html">File Mapper</a>s to specify
 source (input) and destination (output/error) files.  <em>Since Ant 1.6.2</em>
@@ -119,19 +119,19 @@ source (input) and destination (output/error) files.  <em>Since Ant 1.6.2</em>
 input.  Multiple mapping results should concatenate all mapped files as input.
 Mapping will ordinarily be performed on a task-specified sourcefile;
 consult the documentation of the individual task for more details.
 A nested &lt;inputmapper&gt; is not compatible with either of the
 A nested <code>&lt;inputmapper&gt;</code> is not compatible with either of the
 <i>input</i> or <i>inputstring</i> attributes.</p>
 <h4>outputmapper</h4>
 <p>A single <a href="./mapper.html">File Mapper</a> used to redirect process
 output.  Mapping will ordinarily be performed on a task-specified sourcefile;
 consult the documentation of the individual task for more details.
 A nested &lt;outputmapper&gt; is not compatible with the
 A nested <code>&lt;outputmapper&gt;</code> is not compatible with the
 <i>output</i> attribute.</p>
 <h4>errormapper</h4>
 <p>A single <a href="./mapper.html">File Mapper</a> used to redirect error
 output.  Mapping will ordinarily be performed on a task-specified sourcefile;
 consult the documentation of the individual task for more details.
 A nested &lt;errormapper&gt; is not compatible with the
 A nested <code>&lt;errormapper&gt;</code> is not compatible with the
 <i>error</i> attribute.</p>
 <h4>inputfilterchain</h4>
 <p>A <a href="./filterchain.html">FilterChain</a> can be
@@ -149,7 +149,7 @@ Tasks known to support I/O redirection:
 <li><a href="../CoreTasks/apply.html">Apply</a></li>
 <li><a href="../CoreTasks/java.html">Java</a></li>
 </ul>
 <p>The expected behavior of a &lt;redirector&gt; is to a great degree
 <p>The expected behavior of a <code>&lt;redirector&gt;</code> is to a great degree
 dependent on the supporting task.  Any possible points of confusion
 should be noted at the task level.</p>
 <hr />
--- a/docs/manual/CoreTypes/selectors.html
+++ b/docs/manual/CoreTypes/selectors.html
@@ -8,7 +8,7 @@
  <body>
    <h2>Selectors</h2>

    <p>Selectors are a mechanism whereby the files that make up a fileset
    <p>Selectors are a mechanism whereby the files that make up a fileset&lt;depend&gt;<code>
    can be selected based on criteria other than filename as provided
    by the <code>&lt;include&gt;</code> and <code>&lt;exclude&gt;</code>
    tags.</p>
@@ -16,7 +16,7 @@
    <h3>How to use a Selector</h3>

    <p>A selector is an element of FileSet, and appears within it. It can
    also be defined outside of any target by using the &lt;selector&gt; tag
    also be defined outside of any target by using the <code>&lt;selector&gt;</code> tag
    and then using it as a reference.
    </p>

@@ -40,30 +40,30 @@
    <p>The core selectors are:</p>

    <ul>
      <li><a href="#containsselect">&lt;contains&gt;</a> - Select
      <li><a href="#containsselect"><code>&lt;contains&gt;</code></a> - Select
        files that contain a particular text string</li>
      <li><a href="#dateselect">&lt;date&gt;</a> - Select files
      <li><a href="#dateselect"><code>&lt;date&gt;</code></a> - Select files
        that have been modified either before or after a particular date
        and time</li>
      <li><a href="#dependselect">&lt;depend&gt;</a> - Select files
      <li><a href="#dependselect"><code>&lt;depend&gt;</code></a> - Select files
        that have been modified more recently than equivalent files
        elsewhere</li>
      <li><a href="#depthselect">&lt;depth&gt;</a> - Select files
      <li><a href="#depthselect"><code>&lt;depth&gt;</code></a> - Select files
        that appear so many directories down in a directory tree</li>
      <li><a href="#differentselect">&lt;different&gt;</a> - Select files
      <li><a href="#differentselect"><code>&lt;different&gt;</code></a> - Select files
        that are different from those elsewhere</li>
      <li><a href="#filenameselect">&lt;filename&gt;</a> - Select
      <li><a href="#filenameselect"><code>&lt;filename&gt;</code></a> - Select
        files whose name matches a particular pattern. Equivalent to
        the include and exclude elements of a patternset.</li>
      <li><a href="#presentselect">&lt;present&gt;</a> - Select
      <li><a href="#presentselect"><code>&lt;present&gt;</code></a> - Select
        files that either do or do not exist in some other location</li>
      <li><a href="#regexpselect">&lt;containsregexp&gt;</a> - Select
      <li><a href="#regexpselect"><code>&lt;containsregexp&gt;</code></a> - Select
        files that match a regular expression</li>
      <li><a href="#sizeselect">&lt;size&gt;</a> - Select files
      <li><a href="#sizeselect"><code>&lt;size&gt;</code></a> - Select files
        that are larger or smaller than a particular number of bytes.</li>
      <li><a href="#typeselect">&lt;type&gt;</a> - Select files
      <li><a href="#typeselect"><code>&lt;type&gt;</code></a> - Select files
        that are either regular files or directories.</li>
      <li><a href="#modified">&lt;modified&gt;</a> - Select files if
      <li><a href="#modified"><code>&lt;modified&gt;</code></a> - Select files if
        the return value of the configured algorithm is different from that
        stored in a cache.</li>
    </ul>
@@ -310,7 +310,7 @@
    so their dependencies are driven on the absolute state of the files, not just
    a timestamp. For example: anything fetched from a web site, or the output of
    some program. To reduce the amount of checking, when using this task inside
    a &lt;copy&gt; task, set the <tt>preservelastmodified</tt> to propagate the timestamp
    a <code>&lt;copy&gt;</code> task, set the <tt>preservelastmodified</tt> to propagate the timestamp
    from source file to destintaion file.


@@ -469,7 +469,7 @@
              src and target directory trees
          </ul>
          Default is both. Setting this attribute to &quot;srconly&quot;
          is equivalent to wrapping the selector in the &lt;not&gt;
          is equivalent to wrapping the selector in the <code>&lt;not&gt;</code>
          selector container.
        </td>
        <td valign="top" align="center">No</td>
@@ -633,7 +633,7 @@

    <a name="modified"></a>
    <h4>Modified Selector</h4>
    <p>The &lt;modified&gt; selector computes a value for a file, compares that
    <p>The <code>&lt;modified&gt;</code> selector computes a value for a file, compares that
    to the value stored in a cache and select the file, if these two values
    differ.</p>
    <p>Because this selector is highly configurable the order in which the selection is done
@@ -729,7 +729,7 @@
      </tr>
    </table>

    <p>These attributes can be set with nested &lt;param/&gt; tags. With &lt;param/&gt;
    <p>These attributes can be set with nested <code>&lt;param/&gt;</code> tags. With <code>&lt;param/&gt;</code>
    tags you can set other values too - as long as they are named according to
    the following rules: <ul>
        <li> <b> algorithm </b>: same as attribute algorithm </li>
@@ -906,17 +906,17 @@
    <p>The selector containers are:</p>

    <ul>
      <li><a href="#andselect">&lt;and&gt;</a> - select a file only if all
      <li><a href="#andselect"><code>&lt;and&gt;</code></a> - select a file only if all
        the contained selectors select it.
      <li><a href="#majorityselect">&lt;majority&gt;</a> - select a file
      <li><a href="#majorityselect"><code>&lt;majority&gt;</code></a> - select a file
        if a majority of its selectors select it.
      <li><a href="#noneselect">&lt;none&gt;</a> - select a file only if
      <li><a href="#noneselect"><code>&lt;none&gt;</code></a> - select a file only if
        none of the contained selectors select it.
      <li><a href="#notselect">&lt;not&gt;</a> - can contain only one
      <li><a href="#notselect"><code>&lt;not&gt;</code></a> - can contain only one
        selector, and reverses what it selects and doesn't select.
      <li><a href="#orselect">&lt;or&gt;</a> - selects a file if any one
      <li><a href="#orselect"><code>&lt;or&gt;</code></a> - selects a file if any one
        of the contained selectors selects it.
      <li><a href="#selectorselect">&lt;selector&gt;</a> - contains only one
      <li><a href="#selectorselect"><code>&lt;selector&gt;</code></a> - contains only one
        selector and forwards all requests to it without alteration, provided
        that any <code>&quot;if&quot;</code> or
        <code>&quot;unless&quot;</code> conditions are met. This
@@ -932,20 +932,20 @@
    selector elements within a container:</P>

    <ul>
      <li>&lt;and&gt;
      <li>&lt;contains&gt;
      <li>&lt;custom&gt;
      <li>&lt;date&gt;
      <li>&lt;depend&gt;
      <li>&lt;depth&gt;
      <li>&lt;filename&gt;
      <li>&lt;majority&gt;
      <li>&lt;none&gt;
      <li>&lt;not&gt;
      <li>&lt;or&gt;
      <li>&lt;present&gt;
      <li>&lt;selector&gt;
      <li>&lt;size&gt;
      <li><code>&lt;and&gt;</code></li>
      <li><code>&lt;contains&gt;</code></li>
      <li><code>&lt;custom&gt;</code></li>
      <li><code>&lt;date&gt;</code></li>
      <li><code>&lt;depend&gt;</code></li>
      <li><code>&lt;depth&gt;</code></li>
      <li><code>&lt;filename&gt;</code></li>
      <li><code>&lt;majority&gt;</code></li>
      <li><code>&lt;none&gt;</code></li>
      <li><code>&lt;not&gt;</code></li>
      <li><code>&lt;or&gt;</code></li>
      <li><code>&lt;present&gt;</code></li>
      <li><code>&lt;selector&gt;</code></li>
      <li><code>&lt;size&gt;</code></li>
    </ul>

    <a name="andselect"></a>
@@ -1194,7 +1194,7 @@
    <h3>Custom Selectors</h3>

    <p>You can write your own selectors and use them within the selector
    containers by specifying them within the &lt;custom&gt; tag.</p>
    containers by specifying them within the <code>&lt;custom&gt;</code> tag.</p>

    <p>First, you have to write your selector class in Java. The only
    requirement it must meet in order to be a selector is that it implements
@@ -1253,7 +1253,7 @@
 </pre></blockquote>

    <p>A number of core selectors can also be used as custom selectors
    by specifying their attributes using &lt;param&gt; elements. These
    by specifying their attributes using <code>&lt;param&gt;</code> elements. These
    are</p>

    <ul>
--- a/docs/manual/Integration/VAJAntTool.html
+++ b/docs/manual/Integration/VAJAntTool.html
@@ -113,7 +113,7 @@ workspace.</P>
       <td valign="top">remote</TD>
       <td valign="top">
      <P>name and port of a remote tool server. (format:
      &lt;servername&gt;:&lt;port no&gt;).<BR>If this
      <code>&lt;servername&gt;</code>:<code>&lt;port no&gt;</code>).<BR>If this
      attribute is set, the tasks will&nbsp;be executed on the specified tool
      server.&nbsp;</P></TD>
       <td valign="top" align="middle">no</TD></TR>
@@ -210,7 +210,7 @@ files</TD>
       <td valign="top">remote</TD>
       <td valign="top">
      <P>name and port of a remote tool server. (format:
      &lt;servername&gt;:&lt;port no&gt;).<BR>If this
      <code>&lt;servername&gt;</code>:<code>&lt;port no&gt;</code>).<BR>If this
      attribute is set, the tasks will&nbsp;be executed on the specified tool
      server.&nbsp;</P></TD>
       <td valign="top" align="middle">no</TD></TR>
@@ -308,7 +308,7 @@ from the file system into VAJ. These imports can be specified with a fileset.
       <td valign="top">remote</TD>
       <td valign="top">
      <P>name and port of a remote tool server. (format:
      &lt;servername&gt;:&lt;port no&gt;).<BR>If this
      <code>&lt;servername&gt;</code>:<code>&lt;port no&gt;</code>).<BR>If this
      attribute is set, the tasks will&nbsp;be executed on the specified tool
      server.&nbsp;</P></TD>
       <td valign="top" align="middle">no</TD></TR>
@@ -562,7 +562,7 @@ JDK independent by now.
       <td valign="top">
       <P>Added documentation for haltonerror, "*" and "**" version qualifiers.</P></TD></TR></TABLE>
 <hr>
 <center>Copyright &copy 2001-2004 The Apache Software
 <center>Copyright &copy; 2001-2004 The Apache Software
 Foundation. All rights Reserved.</CENTER>
 </body>
 </html>
--- a/docs/manual/OptionalTasks/BorlandEJBTasks.html
+++ b/docs/manual/OptionalTasks/BorlandEJBTasks.html
@@ -64,7 +64,7 @@ his homepage.</p>
      DTD which covers the Borland specific deployment descriptors.
      This should not be necessary if you have borland in your classpath. If you
      do not, you should use a nested
      <a href="ejb.html#ejbjar-dtd">&lt;dtd&gt;</a> element, described
      <a href="ejb.html#ejbjar-dtd"><code>&lt;dtd&gt;</code></a> element, described
      in the ejbjar task documentation.</td>
    <td align="center" valign="middle" width="62">no</td>
  </tr>
@@ -73,7 +73,7 @@ his homepage.</p>
    <td valign="top" width="915"><b>Deprecated</b>. Defines the location of the
      ejb-jar DTD in the class hierarchy. This should not be necessary
      if you have borland in your classpath. If you do not, you should use a
      nested <a href="ejb.html#ejbjar-dtd">&lt;dtd&gt;</a> element,
      nested <a href="ejb.html#ejbjar-dtd"><code>&lt;dtd&gt;</code></a> element,
      described in the ejbjar task
      documentation. </td>
    <td align="center" valign="middle" width="62">no</td>
--- a/docs/manual/OptionalTasks/ccm.html
+++ b/docs/manual/OptionalTasks/ccm.html
@@ -109,7 +109,7 @@ Task to perform a Checkout command to Continuus
 <blockquote>
  <pre>&lt;ccmcheckout  comment=&quot;mycomment&quot;&gt;
  &lt;fileset dir=&quot;lib&quot; &gt;
    &lt;include name=&quot;**/*.jar&quot; /&gt;
    &lt;include name=&quot;**/*.jar&quot;/&gt;
  &lt;/fileset&gt;
 &lt;/ccmcheckout &gt;
  </pre>
@@ -189,7 +189,7 @@ Task to perform an reconfigure command to Continuus.
 <h3>Examples</h3>
 <blockquote>
 <pre>&lt;ccmreconfigure ccmproject=&quot;ANTCCM_TEST#BMO_1&quot;
         verbose=&quot;true&quot; /&gt;
         verbose=&quot;true&quot;/&gt;
 </pre>
 </blockquote>
 <p>Does a Continuus <i>reconfigure</i> on the project <i>ANTCCM_TEST#BMO_1</i>.
@@ -244,7 +244,7 @@ Create a Continuus task.
 <h3>Examples</h3>
 <blockquote>
  <pre>&lt;ccmcreatetask resolver=&quot;${user.name}&quot;
            release=&quot;ANTCCM_TEST&quot; comment=&quot;blahblah&quot; /&gt;
            release=&quot;ANTCCM_TEST&quot; comment=&quot;blahblah&quot;/&gt;
 </pre>
 </blockquote>
 <p>Creates a task for the release <i>ANTCCM_TEST</i> with the
--- a/docs/manual/OptionalTasks/csc.html
+++ b/docs/manual/OptionalTasks/csc.html
@@ -46,7 +46,7 @@
      </td></tr>

      <tr><td><blockquote>
        Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: &lt;csc/&gt; should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested &lt;reference&gt; filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre>&lt;csc optimize=&quot;true&quot; debug=&quot;false&quot; docFile=&quot;documentation.xml&quot; warnLevel=&quot;4&quot; unsafe=&quot;false&quot; targetType=&quot;exe&quot; incremental=&quot;false&quot; mainClass = &quot;MainApp&quot; destFile=&quot;NetApp.exe&quot; &gt; &lt;src dir="src" includes="*.cs" /&gt; &lt;reference file="${testCSC.dll}" /&gt; &lt;define name="RELEASE" /&gt; &lt;define name="DEBUG" if="debug.property"/&gt; &lt;define name="def3" unless="def3.property"/&gt; &lt;/csc&gt; </pre>
        Compiles C# source into executables or modules. csc.exe on Windows or mcs on any other platform must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <code>&lt;csc/&gt;</code> should suffice to produce a debug build of all *.cs files. However, naming an <tt>destFile</tt>stops the csc compiler from choosing an output name from random, and allows the dependency checker to determine if the file is out of date. <p> The task is a directory based task, so attributes like <b>includes="*.cs" </b> and <b>excludes="broken.cs"</b> can be used to control the files pulled in. By default, all *.cs files from the project folder down are included in the command. When this happens the output file -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destFile</tt> seems prudent. <p> <p> For more complex source trees, nested <tt>src</tt> elements can be supplied. When such an element is present, the implicit fileset is ignored. This makes sense, when you think about it :) <p> References to external files can be made through the references attribute, or (since Ant1.6), via nested <code>&lt;reference&gt;</code> filesets. With the latter, the timestamps of the references are also used in the dependency checking algorithm. <p> Example <pre>&lt;csc optimize=&quot;true&quot; debug=&quot;false&quot; docFile=&quot;documentation.xml&quot; warnLevel=&quot;4&quot; unsafe=&quot;false&quot; targetType=&quot;exe&quot; incremental=&quot;false&quot; mainClass = &quot;MainApp&quot; destFile=&quot;NetApp.exe&quot; &gt; &lt;src dir="src" includes="*.cs"/&gt; &lt;reference file="${testCSC.dll}"/&gt; &lt;define name="RELEASE"/&gt; &lt;define name="DEBUG" if="debug.property"/&gt; &lt;define name="def3" unless="def3.property"/&gt; &lt;/csc&gt; </pre>
      </blockquote></td></tr>

    </table>
@@ -503,7 +503,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/dotnet.html
+++ b/docs/manual/OptionalTasks/dotnet.html
@@ -45,7 +45,7 @@ the server's WSDL and running it against the server.
 Axis tasks to create JUnit tests to call the endpoints.

 <li>Patching .NET type libraries to work with more complex IDL than the
 basic &lt;importtypelib&gt; wrapper around tlbimport supports. Hence the
 basic <code>&lt;importtypelib&gt;</code> wrapper around tlbimport supports. Hence the
 disassembler and the reassembler.
 </li>

@@ -148,7 +148,7 @@ executable or library will be rebuilt.
 <h5>Examples</h5>

 <pre>
 &lt;resource file="app.ico" name="icon" /&gt;
 &lt;resource file="app.ico" name="icon"/&gt;
 &lt;resource file="splash.jpg"/&gt;
 &lt;resource name="splash" file="splash.jpg" public="false"/&gt;
 </pre>
@@ -194,7 +194,7 @@ build the code when the defines are likely to be different.
 <h5>Examples</h5>

 <pre>
 &lt;define name="unsafe" /&gt;
 &lt;define name="unsafe"/&gt;
 &lt;define name="debug" if="build.debug"/&gt;
 &lt;define name="dotnet" unless="build.mono"/&gt;
 </pre>
--- a/docs/manual/OptionalTasks/echoproperties.html
+++ b/docs/manual/OptionalTasks/echoproperties.html
@@ -82,7 +82,7 @@ href="../CoreTypes/propertyset.html">propertyset</a>s.</p>
 <p>Report the current properties to the file "my.properties", and will
 fail the build if the file could not be created or written to.</p>
 <blockquote><pre>
  &lt;echoproperties destfile="my.properties" failonerror="false" /&gt;
  &lt;echoproperties destfile="my.properties" failonerror="false"/&gt;
 </pre></blockquote>
 <p>Report the current properties to the file "my.properties", and will
 log a message if the file could not be created or written to, but will still
--- a/docs/manual/OptionalTasks/ejb.html
+++ b/docs/manual/OptionalTasks/ejb.html
@@ -426,7 +426,7 @@ and hence ant, will not complete until the weblogic instance is stopped.</p>

 <h3>Nested Elements</h3>

 <p>The wlrun task supports nested &lt;classpath&gt; and &lt;wlclasspath&gt;
 <p>The wlrun task supports nested <code>&lt;classpath&gt;</code> and <code>&lt;wlclasspath&gt;</code>
 elements to set the respective classpaths.</p>

 <h3>Examples</h3>
@@ -512,7 +512,7 @@ specify the BEA Home to have this task work correctly under 6.0</p>

 <h3>Nested Element</h3>

 <p>The classpath of the wlstop task can be set by a &lt;classpath&gt; nested element.</p>
 <p>The classpath of the wlstop task can be set by a <code>&lt;classpath&gt;</code> nested element.</p>

 <h3>Examples</h3>

@@ -554,7 +554,7 @@ server descriptors are found. For each descriptor found, ejbjar will parse the
 deployment descriptor to determine the necessary class files which implement the
 bean. These files are assembled along with the deployment descriptors into a
 well formed EJB jar file. Any support files which need to be included in the
 generated jar can be added with the &lt;support&gt; nested element. For each
 generated jar can be added with the <code>&lt;support&gt;</code> nested element. For each
 class included in the jar, ejbjar will scan for any super classes or super
 interfaces. These will be added to the generated jar.</p>

@@ -600,10 +600,10 @@ is deployed in separate beans.
 deploying the same bean classes in different beans, with different deployment characteristics.

 <li>ejb-name</li>
 <p> This naming scheme uses the &lt;ejb-name&gt; element from the deployment descriptor to
 <p> This naming scheme uses the <code>&lt;ejb-name&gt;</code> element from the deployment descriptor to
 determine the bean name. In this situation, the descriptors normally use the generic
 descriptor names, such as <code>ejb-jar.xml</code> along with any associated vendor specific descriptor
 names. For example, If the value of the &lt;ejb-name&gt; were to be given in the deployment descriptor
 names. For example, If the value of the <code>&lt;ejb-name&gt;</code> were to be given in the deployment descriptor
 as follows:
 <pre>
 &lt;ejb-jar&gt;
@@ -634,7 +634,7 @@ although that is not mandatory. This scheme can handle multiple beans per jar.

 <li>basejarname</li>
 <p>
 The final scheme supported by the &lt;ejbjar&gt; task is used when you want to specify the generated
 The final scheme supported by the <code>&lt;ejbjar&gt;</code> task is used when you want to specify the generated
 bean jar name directly. In this case the name of the generated jar is specified by the
 &quot;basejarname&quot; attribute. Since all generated beans will have the same name, this task should
 be only used when each descriptor is in its own directory.
@@ -796,22 +796,22 @@ three nested elements. </p>

 <h4>Classpath</h4>

 <p>The &lt;classpath&gt; nested element allows the classpath
 <p>The <code>&lt;classpath&gt;</code> nested element allows the classpath
 to be set. It is useful when setting the classpath from a reference path. In all
 other respects the behaviour is the same as the classpath attribute.</p>

 <a name="ejbjar-dtd"><h4>dtd</h4></a>

 <p>The &lt;dtd&gt; element is used to specify the local location of DTDs to be
 <p>The <code>&lt;dtd&gt;</code> element is used to specify the local location of DTDs to be
 used when parsing the EJB deployment descriptor. Using a local DTD is much
 faster than loading the DTD across the net. If you are running ejbjar behind a
 firewall you may not even be able to access the remote DTD. The supported
 vendor-specific nested elements know the location of the required DTDs within
 the vendor class hierarchy and, in general, this means &lt;dtd&gt; elements are
 the vendor class hierarchy and, in general, this means <code>&lt;dtd&gt;</code> elements are
 not required. It does mean, however, that the vendor's class hierarchy must be
 available in the classpath when Ant is started. If your want to run Ant without
 requiring the vendor classes in the classpath, you would need to use a
 &lt;dtd&gt; element.</p>
 <code>&lt;dtd&gt;</code> element.</p>

 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
@@ -834,10 +834,10 @@ requiring the vendor classes in the classpath, you would need to use a

 <h4>support</h4>

 <p>The &lt;support&gt; nested element is used to supply additional classes
 (files) to be included in the generated jars. The &lt;support&gt; element is a
 <p>The <code>&lt;support&gt;</code> nested element is used to supply additional classes
 (files) to be included in the generated jars. The <code>&lt;support&gt;</code> element is a
 <a href="../CoreTypes/fileset.html">FileSet</a>, so it can either reference a fileset declared elsewhere or it can be
 defined in-place with the appropriate &lt;include&gt; and &lt;exclude&gt; nested
 defined in-place with the appropriate <code>&lt;include&gt;</code> and <code>&lt;exclude&gt;</code> nested
 elements. The files in the support fileset are added into the generated EJB jar
 in the same relative location as their location within the support fileset. Note
 that when ejbjar generates more than one jar file, the support files are added
@@ -914,7 +914,7 @@ generating weblogic EJB jars. Prior to Ant 1.3, the method of locating CMP
 descriptors was to use the ejbjar naming convention. So if your ejb-jar was
 called, Customer-ejb-jar.xml, your weblogic descriptor was called Customer-
 weblogic-ejb-jar.xml and your CMP descriptor had to be Customer-weblogic-cmp-
 rdbms-jar.xml. In addition, the &lt;type-storage&gt; element in the weblogic
 rdbms-jar.xml. In addition, the <code>&lt;type-storage&gt;</code> element in the weblogic
 descriptor had to be set to the standard name META-INF/weblogic-cmp-rdbms-
 jar.xml, as that is where the CMP descriptor was mapped to in the generated
 jar.</p>
@@ -927,7 +927,7 @@ deployment descriptors generated by some tools.</p>
 CMP descriptors, which are then included automatically. This behaviour is
 controlled by the newCMP attribute. Note that if you move to the new method of
 determining CMP descriptors, you will need to update your weblogic deployment
 descriptor's &lt;type-storage&gt; element. In the above example, you would
 descriptor's <code>&lt;type-storage&gt;</code> element. In the above example, you would
 define this as META-INF/Customer-weblogic-cmp-rdbms-jar.xml.</p>

 <table border="1" cellpadding="2" cellspacing="0">
@@ -1029,9 +1029,9 @@ define this as META-INF/Customer-weblogic-cmp-rdbms-jar.xml.</p>
    <td valign="top"><b>Deprecated</b>. Defines the location of the ejb-jar DTD in
                     the weblogic class hierarchy. This should not be necessary if you
                     have weblogic in your classpath. If you do not, you should use a
                     nested &lt;dtd&gt; element, described above. If you do choose
                     nested <code>&lt;dtd&gt;</code> element, described above. If you do choose
                     to use an attribute, you should use a
                     nested &lt;dtd&gt; element.
                     nested <code>&lt;dtd&gt;</code> element.
                     </td>
    <td valign="top" align="center">No.</td>
  </tr>
@@ -1040,7 +1040,7 @@ define this as META-INF/Customer-weblogic-cmp-rdbms-jar.xml.</p>
    <td valign="top"><b>Deprecated</b>. Defines the location of the weblogic-ejb-jar
                     DTD which covers the Weblogic specific deployment descriptors.
                     This should not be necessary if you have weblogic in your
                     classpath. If you do not, you should use a nested &lt;dtd&gt;
                     classpath. If you do not, you should use a nested <code>&lt;dtd&gt;</code>
                     element, described above.
                     </td>
    <td valign="top" align="center">No.</td>
@@ -1050,7 +1050,7 @@ define this as META-INF/Customer-weblogic-cmp-rdbms-jar.xml.</p>
    <td valign="top"><b>Deprecated</b>. Defines the location of the ejb-jar DTD in
                     the weblogic class hierarchy. This should not be necessary if you
                     have weblogic in your classpath. If you do not, you should use a
                     nested &lt;dtd&gt; element, described above.
                     nested <code>&lt;dtd&gt;</code> element, described above.
                     </td>
    <td valign="top" align="center">No.</td>
  </tr>
@@ -1107,9 +1107,9 @@ define this as META-INF/Customer-weblogic-cmp-rdbms-jar.xml.</p>
 </table>

 <p>The weblogic nested element supports three nested elements. The
 first two, &lt;classpath&gt; and &lt;wlclasspath&gt;, are used to set the
 first two, <code>&lt;classpath&gt;</code> and <code>&lt;wlclasspath&gt;</code>, are used to set the
 respective classpaths. These nested elements are useful when setting up
 class paths using reference Ids. The last, &lt;sysproperty&gt;, allows
 class paths using reference Ids. The last, <code>&lt;sysproperty&gt;</code>, allows
 Java system properties to be set during the compiler run. This turns out
 to be necessary for supporting CMP EJB compilation in all environments.
 </p>
@@ -1228,7 +1228,7 @@ This will create only one TOPLink-enabled ejb jar file - 'Address.jar'.</p>
 </pre>

 <p>This final example shows how you would set-up ejbjar under Weblogic 6.0. It also shows the use of the
 &lt;support&gt; element to add support files</p>
 <code>&lt;support&gt;</code> element to add support files</p>

 <pre>
    &lt;ejbjar descriptordir=&quot;${dd.dir}&quot; srcdir=&quot;${build.classes.server}&quot;&gt;
@@ -1485,11 +1485,11 @@ If omitted, it defaults to ".jar". </td>
 </tr>
 </table>

 <p>As noted above, the iplanet element supports additional &lt;classpath&gt;
 <p>As noted above, the iplanet element supports additional <code>&lt;classpath&gt;</code>
 nested elements.</p>
 <h3>
 Examples</h3>
 This example demonstrates the typical use of the &lt;iplanet&gt; nested element.
 This example demonstrates the typical use of the <code>&lt;iplanet&gt;</code> nested element.
 It will name each EJB-JAR using the "basename" prepended to each standard
 EJB descriptor.  For example, if the descriptor named "Account-ejb-jar.xml"
 is processed, the EJB-JAR will be named "Account.jar"
@@ -1553,7 +1553,7 @@ local DTDs are found in the [iAS-install-directory]/dtd directory.

 <h3><a name="ejbjar_jonas">JOnAS (Java Open Application Server) element</a></h3>

 <p>The &lt;jonas&gt; nested element is used to build JOnAS-specific stubs and
 <p>The <code>&lt;jonas&gt;</code> nested element is used to build JOnAS-specific stubs and
 skeletons thanks to the <code>GenIC</code> specific tool, and construct a JAR
 file which may be deployed to the JOnAS Application Server. The build process
 will always determine if the EJB stubs/skeletons and the EJB-JAR file are up to
@@ -1562,13 +1562,13 @@ date, and it will do the minimum amount of work required.</p>
 <p>Like the WebLogic element, a naming convention for the EJB descriptors is
 most commonly used to specify the name for the completed JAR file. For example,
 if the EJB descriptor <code>ejb/Account-ejb-jar.xml</code> is found in the
 descriptor directory, the &lt;jonas&gt; element will search for a JOnAS-specific
 descriptor directory, the <code>&lt;jonas&gt;</code> element will search for a JOnAS-specific
 EJB descriptor file named <code>ejb/Account-jonas-ejb-jar.xml</code> and a JAR
 file named <code>ejb/Account.jar</code> will be written in the destination
 directory. But the &lt;jonas&gt; element can also use the JOnAS naming
 directory. But the <code>&lt;jonas&gt;</code> element can also use the JOnAS naming
 convention. With the same example as below, the EJB descriptor can also be named
 <code>ejb/Account.xml</code> (no base name terminator here) in the descriptor
 directory. Then the &lt;jonas&gt; element will search for a JOnAS-specific EJB
 directory. Then the <code>&lt;jonas&gt;</code> element will search for a JOnAS-specific EJB
 descriptor file called <code>ejb/jonas-Account.xml</code>. This convention do
 not follow strictly the ejb-jar naming convention recommendation but is
 supported for backward compatibility with previous version of JOnAS.</p>
@@ -1698,7 +1698,7 @@ documentation for more details.</p>
  </tbody>
 </table>

 <p>As noted above, the jonas element supports additional &lt;classpath&gt;
 <p>As noted above, the jonas element supports additional <code>&lt;classpath&gt;</code>
 nested elements.</p>

 <h3>Examples</h3>
--- a/docs/manual/OptionalTasks/ftp.html
+++ b/docs/manual/OptionalTasks/ftp.html
@@ -27,7 +27,7 @@ tasks</a>, on how the inclusion/exclusion of files works, and how to
 write patterns.</p>
 <p>
 This task does not currently use the proxy information set by the
 <a href="setproxy.html">&lt;setproxy&gt;</a> task, and cannot go through
 <a href="setproxy.html"><code>&lt;setproxy&gt;</code></a> task, and cannot go through
 a firewall via socks. 
 <p>
 <b>Warning: </b> there have been problems reported concerning the ftp get with newer attribute.
--- a/docs/manual/OptionalTasks/ilasm.html
+++ b/docs/manual/OptionalTasks/ilasm.html
@@ -46,7 +46,7 @@
      </td></tr>

      <tr><td><blockquote>
        Assembles .NET Intermediate Language files. ilasm.exe must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> <p> All parameters are optional: &lt;il/&gt; should suffice to produce a debug build of all *.il files. The option set is roughly compatible with the CSharp class; even though the command line options are only vaguely equivalent. [The low level commands take things like /OUT=file, csc wants /out:file ... /verbose is used some places; /quiet here in ildasm... etc.] It would be nice if someone made all the command line tools consistent (and not as brittle as the java cmdline tools) <p> <p> The task is a directory based task, so attributes like <b>includes="*.il" </b> and <b>excludes="broken.il"</b> can be used to control the files pulled in. You can also use nested &lt;src&gt filesets to refer to source. <p>
        Assembles .NET Intermediate Language files. ilasm.exe must be on the execute path, unless another executable or the full path to that executable is specified in the <tt>executable</tt> parameter <p> <p> All parameters are optional: <code>&lt;il/&gt;</code> should suffice to produce a debug build of all *.il files. The option set is roughly compatible with the CSharp class; even though the command line options are only vaguely equivalent. [The low level commands take things like /OUT=file, csc wants /out:file ... /verbose is used some places; /quiet here in ildasm... etc.] It would be nice if someone made all the command line tools consistent (and not as brittle as the java cmdline tools) <p> <p> The task is a directory based task, so attributes like <b>includes="*.il" </b> and <b>excludes="broken.il"</b> can be used to control the files pulled in. You can also use nested &lt;src&gt filesets to refer to source. <p>
      </blockquote></td></tr>

    </table>
@@ -277,7 +277,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/ildasm.html
+++ b/docs/manual/OptionalTasks/ildasm.html
@@ -327,7 +327,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/importtypelib.html
+++ b/docs/manual/OptionalTasks/importtypelib.html
@@ -195,7 +195,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/jdepend.html
+++ b/docs/manual/OptionalTasks/jdepend.html
@@ -95,10 +95,10 @@ href="../using.html#path">PATH like structures</a>, and
 <p><code>&lt;sourcespath&gt;</code> is used to define the paths of the
 source code to analyze, but it is deprecated. With version 2.5 of
 JDepend, only class files are analyzed. The nested element
 &lt;classespath&gt; replaces &lt;sourcespath&gt; and is used to define
 the paths of compiled class code to analyze; the &lt;sourcespath&gt;
 <code>&lt;classespath&gt;</code> replaces <code>&lt;sourcespath&gt;</code> and is used to define
 the paths of compiled class code to analyze; the <code>&lt;sourcespath&gt;</code>
 variable is still available in case you are using an earlier version
 of JDepend.  The &lt;exclude&gt; element can be used to set packages
 of JDepend.  The <code>&lt;exclude&gt;</code> element can be used to set packages
 to ignore (requires JDepend 2.5 or above).</p>

 <h3>Examples</h3>
--- a/docs/manual/OptionalTasks/jsharpc.html
+++ b/docs/manual/OptionalTasks/jsharpc.html
@@ -443,7 +443,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/jspc.html
+++ b/docs/manual/OptionalTasks/jspc.html
@@ -26,7 +26,7 @@ or simply to syntax check the pages without deploying them.
 In most cases, a javac task is usually the next stage in the build process.
 The task does basic dependency checking to prevent unnecessary recompilation -this
 checking compares source and destination timestamps, and does not factor
 in class or taglib dependencies, or &lt;jsp:include&gt; references.
 in class or taglib dependencies, or <code>&lt;jsp:include&gt;</code> references.

 <p>
 By default the task uses the Jasper JSP compiler. This
@@ -233,7 +233,7 @@ When used, the task hands off all dependency checking to the compiler.
      package="com.i3sp.jsp"
      compiler="jasper41"
      verbose="9"&gt;
  &lt;include name="**/*.jsp" /&gt;
  &lt;include name="**/*.jsp"/&gt;
 &lt;/jspc&gt;
 </pre>
 Build all jsp pages under src/war into the destination /gensrc, in a
@@ -246,7 +246,7 @@ package hierarchy beginning with com.i3sp.jsp.
      srcdir="src"
      compiler="jasper41"
      package="com.i3sp.jsp"&gt;
  &lt;include name="**/*.jsp" /&gt;
  &lt;include name="**/*.jsp"/&gt;
 &lt;/jspc&gt;
 &lt;depend
         srcdir="interim"
--- a/docs/manual/OptionalTasks/native2ascii.html
+++ b/docs/manual/OptionalTasks/native2ascii.html
@@ -25,10 +25,10 @@
      If <em>ext</em> is specified, then output files are renamed
      to use it as a new extension.
      More sophisticated file name translations can be achieved using a nested
      <em>&lt;mapper&gt;</em> element. By default an
      <em><code>&lt;mapper&gt;</code></em> element. By default an
      <a href="../CoreTypes/mapper.html#identity-mapper">identity mapper</a> will be used.
      If <em>dest</em> and <em>src</em> point to the same directory,
      the <em>ext</em> attribute or a nested <em>&lt;mapper&gt;</em>
      the <em>ext</em> attribute or a nested <em><code>&lt;mapper&gt;</code></em>
      is required.
    </p>

--- a/docs/manual/OptionalTasks/pvcstask.html
+++ b/docs/manual/OptionalTasks/pvcstask.html
@@ -240,7 +240,7 @@ The following set-up extracts the latest version of the files in the pvcs reposi
  Total time: 19 seconds</pre>

 This next example extracts the latest version of the files in the pvcs
 repository from two projects using nested &lt;pvcsproject&gt; elements.
 repository from two projects using nested <code>&lt;pvcsproject&gt;</code> elements.
 <pre>
  &lt;!-- ===================================================================--&gt;
  &lt;!-- Get latest from myprj and myprj2                                   --&gt;
@@ -273,7 +273,7 @@ repository from two projects using nested &lt;pvcsproject&gt; elements.
  Total time: 22 seconds</pre>

 <hr WIDTH="100%">
 <p align="center">Copyright &copy; 2001-2003 Apache Software
 <p align="center">Copyright &copy; 2001-2004 Apache Software
 Foundation. All rights Reserved.</p>
 <p>PVCS is a registered trademark of MERANT.</p>
 </body>
--- a/docs/manual/OptionalTasks/replaceregexp.html
+++ b/docs/manual/OptionalTasks/replaceregexp.html
@@ -32,18 +32,18 @@ See details in the documentation of the <a href="../CoreTypes/regexp.html#implem
  <tr>
    <td valign="top">file</td>
    <td valign="top">file for which the regular expression should be replaced.</td>
    <td align="center">Yes if no nested &lt;fileset&gt; is used</td>
    <td align="center">Yes if no nested <code>&lt;fileset&gt;</code> is used</td>
  </tr>
  <tr>
    <td valign="top">match</td>
    <td valign="top">The regular expression pattern to match in the file(s)</td>
    <td align="center">Yes, if no nested &lt;regexp&gt; is used</td>
    <td align="center">Yes, if no nested <code>&lt;regexp&gt;</code> is used</td>
  </tr>
  <tr>
    <td valign="top">replace</td>
    <td valign="top">The substitution pattern to place in the file(s) in place
                     of the regular expression.</td>
    <td align="center">Yes, if no nested &lt;substitution&gt; is used</td>
    <td align="center">Yes, if no nested <code>&lt;substitution&gt;</code> is used</td>
  </tr>
  <tr>
    <td valign="top">flags</td>
@@ -115,7 +115,7 @@ value, in all files ending in <code>.properties</code> in the current directory<

 <blockquote>
 <pre>&lt;replaceregexp match="\s+" replace=" " flags="g" byline="true"&gt;
    &lt;fileset dir="${html.dir}" includes="**/*.html" /&gt;
    &lt;fileset dir="${html.dir}" includes="**/*.html"/&gt;
 &lt;/replaceregexp&gt;
 </pre></blockquote>
 <p>replaces all whitespaces (blanks, tabs, etc) by one blank remaining the
--- a/docs/manual/OptionalTasks/rexec.html
+++ b/docs/manual/OptionalTasks/rexec.html
@@ -66,7 +66,7 @@ timeout specified for the task as a whole. It also has a <tt>string</tt>
 attribute, which is an alternative to specifying the string as 
 a text element.
 </p>
 <i>It is not necessary to declare a closing &lt;read&gt; element like for the Telnet task. The connection is not broken until the command has completed and
 <i>It is not necessary to declare a closing <code>&lt;read&gt;</code> element like for the Telnet task. The connection is not broken until the command has completed and
 the input stream (output of the command) is terminated.
 </i>
 <h4>write</h4>
--- a/docs/manual/OptionalTasks/scp.html
+++ b/docs/manual/OptionalTasks/scp.html
@@ -185,7 +185,7 @@ authentication.</b></p>

 <p><b>Copy a remote directory to a local directory</b></p>
 <pre>
  &lt;scp file=&quot;user:password@somehost:/home/chuck/*&quot; todir=&quot;/home/sara&quot; /&gt;
  &lt;scp file=&quot;user:password@somehost:/home/chuck/*&quot; todir=&quot;/home/sara&quot;/&gt;
 </pre>

 <p><b>Copy a local directory to a remote directory</b></p>
--- a/docs/manual/OptionalTasks/script.html
+++ b/docs/manual/OptionalTasks/script.html
@@ -19,7 +19,7 @@ accessible from the script, using either their <code>name</code> or
 valid Java identifiers, that is).
 The name "project" is a pre-defined reference to the Project, which can be
 used instead of the project name. The name "self" is a pre-defined reference to the actual
 &lt;script&gt;-Task instance.<br/>From these objects you have access to the Ant Java API, see the
 <code>&lt;script&gt;</code>-Task instance.<br/>From these objects you have access to the Ant Java API, see the
 <a href="../api/index.html">JavaDoc</a> (especially for
 <a href="../api/org/apache/tools/ant/Project.html">Project</a> and
 <a href="../api/org/apache/tools/ant/taskdefs/optional/Script.html">Script</a>) for more information.</p>
@@ -187,7 +187,7 @@ BUILD SUCCESSFUL
 </pre></blockquote>

 <p>Now a more complex example using the Java API and the Ant API. The goal is to list the
 filesizes of all files a &lt;fileset/&gt; caught.</p>
 filesizes of all files a <code>&lt;fileset/&gt;</code> caught.</p>
 <blockquote><pre>

 &lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
@@ -209,7 +209,7 @@ filesizes of all files a &lt;fileset/&gt; caught.</p>
      includes = <font color=blue>MyProject</font>.getProperty("fs.includes");
      excludes = <font color=blue>self.getProject()</font>  .<font color=blue>getProperty("fs.excludes")</font>;

      // Create a &lt;fileset dir="" includes="" /&gt;
      // Create a &lt;fileset dir="" includes=""/&gt;
      fs = project.<font color=blue>createDataType("fileset")</font>;
      fs.setDir( new File(dir) );
      <font color=blue>fs.setIncludes(includes)</font>;
@@ -245,16 +245,16 @@ For other packages you have to prefix the full classified name with <i>Package</
 For example ant´s <i>FileUtil</i> class can be imported with
 <code>importClass(<b>Package</b>.org.apache.tools.ant.util.FileUtils)</code>
 <br>
 The &lt;script&gt; task populates the Project instance under
 The <code>&lt;script&gt;</code> task populates the Project instance under
 the name <i>project</i>, so we can use that reference. Another way is to use its given name
 or getting its reference from the task itself.<br>
 The Project provides methods for accessing and setting properties, creating DataTypes and
 Tasks and much more.<br>
 After creating a FileSet object we initialize that by calling its set-methods. Then we can
 use that object like a normal Ant task (&lt;copy&gt; for example).<br>
 use that object like a normal Ant task (<code>&lt;copy&gt;</code> for example).<br>
 For getting the size of a file we instantiate a <code>java.io.File</code>. So we are using
 normal Java API here.<br>
 Finally we use the &lt;echo&gt; task for producing the output. The task is not executed by
 Finally we use the <code>&lt;echo&gt;</code> task for producing the output. The task is not executed by
 its execute() method, because the perform() method (implemented in Task itself) does the
 appropriate logging before and after invoking execute().
 </p>
--- a/docs/manual/OptionalTasks/scriptdef.html
+++ b/docs/manual/OptionalTasks/scriptdef.html
@@ -27,7 +27,7 @@ Ant distribution. See
 for more information.</p>

 <p>The attributes and nested elements supported by the task may be defined
 using &lt;attribute&gt; and &lt;element&gt; nested elements. These are
 using <code>&lt;attribute&gt;</code> and <code>&lt;element&gt;</code> nested elements. These are
 available to the script that implements the task as two collection style
 script variables <code>attributes</code> and <code>elements</code>. The
 elements in the <code>attributes</code> collection may be accessed by the
@@ -45,7 +45,7 @@ to use "someattribute" to retrieve the attribute's value from the
  It can be used for logging purposes</p>
 <p>The name "project" is a pre-defined reference to the Ant Project. For
 more information on writing scripts, please refer to the
 <a href="script.html">&lt;script&gt;</a> task
 <a href="script.html"><code>&lt;script&gt;</code></a> task
 </p>


@@ -183,7 +183,7 @@ would result in this error
 </p>

 <p><code>build.xml:15: SyntaxError: missing } in compound
 statement (scriptdef &lt;scripttest2&gt;; line 10)</code></p>
 statement (scriptdef <code>&lt;scripttest2&gt;</code>; line 10)</code></p>

 <p>
 Script errors are only detected when a script task is actually executed.
--- a/docs/manual/OptionalTasks/serverdeploy.html
+++ b/docs/manual/OptionalTasks/serverdeploy.html
@@ -138,7 +138,7 @@ possible.
 </p>

 <h3>Nested Elements</h3>
 <p>The generic element supports nested &lt;arg&gt; and &lt;jvmarg&gt; elements.</p>
 <p>The generic element supports nested <code>&lt;arg&gt;</code> and <code>&lt;jvmarg&gt;</code> elements.</p>

 <h3>Example</h3>

@@ -279,7 +279,7 @@ task.
 </table>

 <h3>Nested Elements</h3>
 <p>The jonas element supports nested &lt;arg&gt; and &lt;jvmarg&gt; elements.</p>
 <p>The jonas element supports nested <code>&lt;arg&gt;</code> and <code>&lt;jvmarg&gt;</code> elements.</p>


 <h3>Examples</h3>
--- a/docs/manual/OptionalTasks/setproxy.html
+++ b/docs/manual/OptionalTasks/setproxy.html
@@ -211,7 +211,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/splash.html
+++ b/docs/manual/OptionalTasks/splash.html
@@ -42,7 +42,7 @@ whilst waiting for your builds to complete...</p>
 The following properties can be used to configure the proxy settings to retrieve
 an image from behind a firewall. However, the settings apply not just to this
 task, but to all following tasks. Therefore they are now mostly deprecated in 
 preference to the &lt;setproxy&gt; task, that makes it clear to readers of
 preference to the <code>&lt;setproxy&gt;</code> task, that makes it clear to readers of
 the build exactly what is going on. We say mostly as this task's support
 includes proxy authentication, so you may still need to use its
 proxy attributes.
--- a/docs/manual/OptionalTasks/stylebook.html
+++ b/docs/manual/OptionalTasks/stylebook.html
@@ -15,7 +15,7 @@ are required to run stylebook.</p>
 <p><b>Note:</b> This task depends on external libraries not included in the Ant distribution.
 See <a href="../install.html#librarydependencies">Library Dependencies</a> for more information.</p>
 <p>
 Being extended from &lt;Java&gt;, all the parent's attributes
 Being extended from <code>&lt;Java&gt;</code>, all the parent's attributes
 and options are available. Do not set any apart from the <tt>classpath</tt>
 as they are not guaranteed to be there in future.
 </p>
@@ -47,7 +47,7 @@ See <a href="../install.html#librarydependencies">Library Dependencies</a> for m
  </tr>
 </table>
 <p>
 The user can also specify the nested &lt;classpath&gt; element which defines classpath 
 The user can also specify the nested <code>&lt;classpath&gt;</code> element which defines classpath 
 in which the task is executed.</p>

 <h3>Examples</h3>
--- a/docs/manual/OptionalTasks/symlink.html
+++ b/docs/manual/OptionalTasks/symlink.html
@@ -80,14 +80,14 @@ set of links to record, or a set of property files to create links from. </p>
  "dir.links"</p>
  <pre>
  &lt;symlink action="record" linkfilename="dir.links"&gt;
     &lt;fileset dir="${dir.top}" includes="subdir&#47;**" /&gt;
     &lt;fileset dir="${dir.top}" includes="subdir&#47;**"/&gt;
  &lt;/symlink&gt;
  </pre>
 
  <p> Recreate the links recorded in the previous example:</p>
  <pre>
  &lt;symlink action="recreate"&gt;
     &lt;fileset dir="${dir.top}" includes="subdir&#47;**&#47;dir.links" /&gt;  
     &lt;fileset dir="${dir.top}" includes="subdir&#47;**&#47;dir.links"/&gt;  
  &lt;/symlink&gt;
  </pre>
 
@@ -117,7 +117,7 @@ set of links to record, or a set of property files to create links from. </p>
  <code>link=subdir/foo.bar</code> and restored as
  <code>link --> subdir/foo.bar</code></p>

 <hr><p align="center">Copyright &copy; 2002 Apache Software
 <hr><p align="center">Copyright &copy; 2002,2004 Apache Software
 Foundation.  All rights Reserved.</p>

 </body>
--- a/docs/manual/OptionalTasks/telnet.html
+++ b/docs/manual/OptionalTasks/telnet.html
@@ -69,7 +69,7 @@ attribute, which is an alternative to specifying the string as
 a text element.
 </p>
 <i>Always declare an opening and closing
 &lt;read&gt; element to ensure that statements are not sent before
 <code>&lt;read&gt;</code> element to ensure that statements are not sent before
 the connection is ready, and that the connection is not broken before
 the final command has completed.
 </i>
@@ -105,7 +105,7 @@ This task can be rewritten as:
 &lt;/telnet&gt;
 </pre></blockquote>

 A timeout can be specified at the &lt;telnet&gt; level or at the &lt;read&gt; level. 
 A timeout can be specified at the <code>&lt;telnet&gt;</code> level or at the <code>&lt;read&gt;</code> level. 
 This will connect, issue a sleep command that is suppressed from displaying and wait 
 10 seconds before quitting.
 <blockquote><pre>
--- a/docs/manual/OptionalTasks/test.html
+++ b/docs/manual/OptionalTasks/test.html
@@ -53,7 +53,7 @@ Library Dependencies</a> for more information.
  </tr>
 </table>
 <p>
 The user can also specify the nested &lt;classpath&gt; element which defines classpath 
 The user can also specify the nested <code>&lt;classpath&gt;</code> element which defines classpath 
 in which the task is executed. The user also specifies a subelement per testlet executed
 which has content that specifies tasklet classname.</p>

--- a/docs/manual/OptionalTasks/vbc.html
+++ b/docs/manual/OptionalTasks/vbc.html
@@ -46,7 +46,7 @@
      </td></tr>

      <tr><td><blockquote>
        This task compiles Visual Basic.NET source into executables or modules. The task requires vbc.exe on the execute path, unless it or an equivalent program is specified in the <tt>executable</tt> parameter <p> All parameters are optional: &lt;vbc/&gt; should suffice to produce a debug build of all *.vb files. <p> The task is a directory based task, so attributes like <tt>includes=&quot;**\/*.vb&quot;</tt> and <tt>excludes=&quot;broken.vb&quot;</tt> can be used to control the files pulled in. By default, all *.vb files from the project folder down are included in the command. When this happens the destFile -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destfile</tt> is prudent. </p> <p> Also, dependency checking only works if destfile is set. As with &lt;csc&gt; nested <tt>src</tt> filesets of source, reference filesets, definitions and resources can be provided. <p> Example </p> <pre>&lt;vbc optimize=&quot;true&quot; debug=&quot;false&quot; warnLevel=&quot;4&quot; targetType=&quot;exe&quot; definitions=&quot;RELEASE&quot; excludes=&quot;src/unicode_class.vb&quot; mainClass = &quot;MainApp&quot; destFile=&quot;NetApp.exe&quot; optionExplicit=&quot;true&quot; optionCompare=&quot;text&quot; references="System.Xml,System.Web.Xml" &gt; &lt;reference file="${testCSC.dll}" /&gt; &lt;define name="RELEASE" /&gt; &lt;define name="DEBUG" if="debug.property"/&gt; &lt;define name="def3" unless="def2.property"/&gt; &lt;/vbc&gt; </pre>
        This task compiles Visual Basic.NET source into executables or modules. The task requires vbc.exe on the execute path, unless it or an equivalent program is specified in the <tt>executable</tt> parameter <p> All parameters are optional: <code>&lt;vbc/&gt;</code> should suffice to produce a debug build of all *.vb files. <p> The task is a directory based task, so attributes like <tt>includes=&quot;**\/*.vb&quot;</tt> and <tt>excludes=&quot;broken.vb&quot;</tt> can be used to control the files pulled in. By default, all *.vb files from the project folder down are included in the command. When this happens the destFile -if not specified- is taken as the first file in the list, which may be somewhat hard to control. Specifying the output file with <tt>destfile</tt> is prudent. </p> <p> Also, dependency checking only works if destfile is set. As with <code>&lt;csc&gt;</code> nested <tt>src</tt> filesets of source, reference filesets, definitions and resources can be provided. <p> Example </p> <pre>&lt;vbc optimize=&quot;true&quot; debug=&quot;false&quot; warnLevel=&quot;4&quot; targetType=&quot;exe&quot; definitions=&quot;RELEASE&quot; excludes=&quot;src/unicode_class.vb&quot; mainClass = &quot;MainApp&quot; destFile=&quot;NetApp.exe&quot; optionExplicit=&quot;true&quot; optionCompare=&quot;text&quot; references="System.Xml,System.Web.Xml" &gt; &lt;reference file="${testCSC.dll}"/&gt; &lt;define name="RELEASE"/&gt; &lt;define name="DEBUG" if="debug.property"/&gt; &lt;define name="def3" unless="def2.property"/&gt; &lt;/vbc&gt; </pre>
      </blockquote></td></tr>

    </table>
@@ -479,7 +479,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTasks/vss.html
+++ b/docs/manual/OptionalTasks/vss.html
@@ -418,7 +418,7 @@ Task to perform HISTORY commands to Microsoft Visual SourceSafe.
 <blockquote>
  <pre>
 &lt;tstamp&gt;
  &lt;format property=&quot;to.tstamp&quot; pattern=&quot;M-d-yy;h:mma&quot; /&gt;
  &lt;format property=&quot;to.tstamp&quot; pattern=&quot;M-d-yy;h:mma&quot;/&gt;
 &lt;/tstamp&gt;

 &lt;vsshistory vsspath=&quot;$/myProject&quot; recursive=&quot;true&quot;
--- a/docs/manual/OptionalTasks/wsdltodotnet.html
+++ b/docs/manual/OptionalTasks/wsdltodotnet.html
@@ -46,7 +46,7 @@
      </td></tr>

      <tr><td><blockquote>
        Converts a WSDL file or URL resource into a .NET language. Why add a wrapper to the MS WSDL tool? So that you can verify that your web services, be they written with Axis or anyone else's SOAP toolkit, work with .NET clients. This task is dependency aware when using a file as a source and destination; so if you &lt;get&gt; the file (with <code>usetimestamp="true"</code>) then you only rebuild stuff when the WSDL file is changed. Of course, if the server generates a new timestamp every time you ask for the WSDL, this is not enough...use the &lt;filesmatch&gt; &lt;condition&gt; to to byte for byte comparison against a cached WSDL file then make the target conditional on that test failing. See "Creating an XML Web Service Proxy", "wsdl.exe" docs in the framework SDK documentation
        Converts a WSDL file or URL resource into a .NET language. Why add a wrapper to the MS WSDL tool? So that you can verify that your web services, be they written with Axis or anyone else's SOAP toolkit, work with .NET clients. This task is dependency aware when using a file as a source and destination; so if you <code>&lt;get&gt;</code> the file (with <code>usetimestamp="true"</code>) then you only rebuild stuff when the WSDL file is changed. Of course, if the server generates a new timestamp every time you ask for the WSDL, this is not enough...use the <code>&lt;filesmatch&gt;</code> <code>&lt;condition&gt;</code> to to byte for byte comparison against a cached WSDL file then make the target conditional on that test failing. See "Creating an XML Web Service Proxy", "wsdl.exe" docs in the framework SDK documentation
      </blockquote></td></tr>

    </table>
@@ -219,7 +219,7 @@
  <tr>
    <td>
      <div align="center"><font color="#525D76" size="-1"><em>
        Copyright &#169; 2000-2003, Apache Software Foundation
        Copyright &copy; 2000-2004, The Apache Software Foundation. All Rights Reserved.
      </em></font></div>
    </td>
  </tr>
--- a/docs/manual/OptionalTypes/classfileset.html
+++ b/docs/manual/OptionalTypes/classfileset.html
@@ -44,7 +44,7 @@ to those supported by the

 <h4>Root</h4>
 <p>
 When more than one root class is required, multiple nested &lt;root&gt; elements
 When more than one root class is required, multiple nested <code>&lt;root&gt;</code> elements
 may be used
 </p>
 <table border="1" cellpadding="2" cellspacing="0">
@@ -71,7 +71,7 @@ relative location of the classfile in the fileset. So, the file
 <h4>Examples</h4>
 <blockquote><pre>
 &lt;classfileset id=&quot;reqdClasses" dir=&quot;${classes.dir}&quot;&gt;
  &lt;root classname=&quot;org.apache.tools.ant.Project&quot; /&gt;
  &lt;root classname=&quot;org.apache.tools.ant.Project&quot;/&gt;
 &lt;/classfileset&gt;
 </pre></blockquote>

--- a/docs/manual/develop.html
+++ b/docs/manual/develop.html
@@ -210,7 +210,7 @@ the implementation of your Java virtual machine.</p>

  <h3><a name="nestedtype">Nested Types</a></h3>
 If your task needs to nest an arbitary type that has been defined
  using &lt;typedef&gt; you have two options.
  using <code>&lt;typedef&gt;</code> you have two options.
  <ol>
    <li><code>public void add(Type type)</code></li>
    <li><code>public void addConfigured(Type type)</code></li>
@@ -435,9 +435,9 @@ for the following events</P>
 </ul>

 <p>If the build file invokes another build file via <a
 href="CoreTasks/ant.html">&lt;ant&gt;</a> or <a
 href="CoreTasks/subant.html">&lt;subant&gt;</a> or uses <a
 href="CoreTasks/antcall.html">&lt;antcall&gt;</a>, you are creating a
 href="CoreTasks/ant.html"><code>&lt;ant&gt;</code></a> or <a
 href="CoreTasks/subant.html"><code>&lt;subant&gt;</code></a> or uses <a
 href="CoreTasks/antcall.html"><code>&lt;antcall&gt;</code></a>, you are creating a
 new Ant "project" that will send target and task level events of its
 own but never sends build started/finished events.  Ant 1.6.2
 introduces an extension of the BuildListener interface named
--- a/docs/manual/dirtasks.html
+++ b/docs/manual/dirtasks.html
@@ -185,39 +185,39 @@ information.</p>
 the rules given here. This list, a subset of those, is a list of standard ant
 tasks that can act as an implicit fileset:</p>
 <ul>
  <li><a href="CoreTasks/checksum.html">&lt;checksum&gt;</a></li>
  <li><a href="CoreTasks/copydir.html">&lt;copydir&gt;</a> (deprecated)</li>
  <li><a href="CoreTasks/delete.html">&lt;delete&gt;</a></li>
  <li><a href="CoreTasks/dependset.html">&lt;dependset&gt;</a></li>
  <li><a href="CoreTasks/fixcrlf.html">&lt;fixcrlf&gt;</a></li>
  <li><a href="CoreTasks/javac.html">&lt;javac&gt;</a></li>
  <li><a href="CoreTasks/replace.html">&lt;replace&gt;</a></li>
  <li><a href="CoreTasks/rmic.html">&lt;rmic&gt;</a></li>
  <li><a href="CoreTasks/style.html">&lt;style&gt; (aka &lt;xslt&gt;)</a></li>
  <li><a href="CoreTasks/tar.html">&lt;tar&gt;</a></li>
  <li><a href="CoreTasks/zip.html">&lt;zip&gt;</a></li>
  <li><a href="OptionalTasks/ejb.html#ddcreator">&lt;ddcreator&gt;</a></li>
  <li><a href="OptionalTasks/ejb.html#ejbjar">&lt;ejbjar&gt;</a></li>
  <li><a href="OptionalTasks/ejb.html#ejbc">&lt;ejbc&gt;</a></li>
  <li><a href="OptionalTasks/cab.html">&lt;cab&gt;</a></li>
  <li><a href="OptionalTasks/icontract.html">&lt;icontract&gt;</a></li>
  <li><a href="OptionalTasks/native2ascii.html">&lt;native2ascii&gt;</a></li>
  <li><a href="OptionalTasks/netrexxc.html">&lt;netrexxc&gt;</a></li>
      <li><a href="CoreTasks/checksum.html"><code>&lt;checksum&gt;</code></a></li>
  <li><a href="CoreTasks/copydir.html"><code>&lt;copydir&gt;</code></a> (deprecated)</li>
  <li><a href="CoreTasks/delete.html"><code>&lt;delete&gt;</code></a></li>
  <li><a href="CoreTasks/dependset.html"><code>&lt;dependset&gt;</code></a></li>
  <li><a href="CoreTasks/fixcrlf.html"><code>&lt;fixcrlf&gt;</code></a></li>
  <li><a href="CoreTasks/javac.html"><code>&lt;javac&gt;</code></a></li>
  <li><a href="CoreTasks/replace.html"><code>&lt;replace&gt;</code></a></li>
  <li><a href="CoreTasks/rmic.html"><code>&lt;rmic&gt;</code></a></li>
  <li><a href="CoreTasks/style.html"><code>&lt;style&gt;</code> (aka <code>&lt;xslt&gt;</code>)</a></li>
  <li><a href="CoreTasks/tar.html"><code>&lt;tar&gt;</code></a></li>
  <li><a href="CoreTasks/zip.html"><code>&lt;zip&gt;</code></a></li>
  <li><a href="OptionalTasks/ejb.html#ddcreator"><code>&lt;ddcreator&gt;</code></a></li>
  <li><a href="OptionalTasks/ejb.html#ejbjar"><code>&lt;ejbjar&gt;</code></a></li>
  <li><a href="OptionalTasks/ejb.html#ejbc"><code>&lt;ejbc&gt;</code></a></li>
  <li><a href="OptionalTasks/cab.html"><code>&lt;cab&gt;</code></a></li>
  <li><a href="OptionalTasks/icontract.html"><code>&lt;icontract&gt;</code></a></li>
  <li><a href="OptionalTasks/native2ascii.html"><code>&lt;native2ascii&gt;</code></a></li>
  <li><a href="OptionalTasks/netrexxc.html"><code>&lt;netrexxc&gt;</code></a></li>
  <li>
    <a href="OptionalTasks/renameextensions.html">&lt;renameextensions&gt;</a>
    <a href="OptionalTasks/renameextensions.html"><code>&lt;renameextensions&gt;</code></a>
  </li>
  <li><a href="OptionalTasks/depend.html">&lt;depend&gt;</a></li>
  <li><a href="OptionalTasks/dotnet.html">&lt;ilasm&gt;</a></li>
  <li><a href="OptionalTasks/dotnet.html">&lt;csc&gt;</a></li>
  <li><a href="OptionalTasks/dotnet.html">&lt;vbc&gt;</a></li>
  <li><a href="OptionalTasks/translate.html">&lt;translate&gt;</a></li>
  <li><a href="OptionalTasks/depend.html"><code>&lt;depend&gt;</code></a></li>
  <li><a href="OptionalTasks/dotnet.html"><code>&lt;ilasm&gt;</code></a></li>
  <li><a href="OptionalTasks/dotnet.html"><code>&lt;csc&gt;</code></a></li>
  <li><a href="OptionalTasks/dotnet.html"><code>&lt;vbc&gt;</code></a></li>
  <li><a href="OptionalTasks/translate.html"><code>&lt;translate&gt;</code></a></li>
  <li>
    <a href="Integration/VAJAntTool.html#vajexport">&lt;vajexport&gt;</a>
    <a href="Integration/VAJAntTool.html#vajexport"><code>&lt;vajexport&gt;</code></a>
  </li>
  <li>&lt;image&gt;</li>
  <li><a href="OptionalTasks/jlink.html">&lt;jlink&gt;</a> (deprecated)</li>
  <li><a href="OptionalTasks/jspc.html">&lt;jspc&gt;</a></li>
  <li><a href="OptionalTasks/wljspc.html">&lt;wljspc&gt;</a></li>
  <li><code>&lt;image&gt;</code></li>
  <li><a href="OptionalTasks/jlink.html"><code>&lt;jlink&gt;</code></a> (deprecated)</li>
  <li><a href="OptionalTasks/jspc.html"><code>&lt;jspc&gt;</code></a></li>
  <li><a href="OptionalTasks/wljspc.html"><code>&lt;wljspc&gt;</code></a></li>
 </ul>

 <h3><a name="examples">Examples</a></h3>
--- a/docs/manual/intro.html
+++ b/docs/manual/intro.html
@@ -41,7 +41,7 @@ able to construct a shell command such as
 gives you the ability to be cross-platform - to work anywhere and
 everywhere. And
 hey, if you really need to execute a shell command, Ant has an
 &lt;exec&gt; task that
 <code>&lt;exec&gt;</code> task that
 allows different commands to be executed based on the OS it is executing
 on.</p>

--- a/docs/manual/platform.html
+++ b/docs/manual/platform.html
@@ -50,7 +50,7 @@ wierd errors about missing files, this is the problem.
 archived, because Java does not let it read or write the permissions.
 Use <tt>&lt;chmod&gt;</tt> to set permissions, and when creating a 
 tar archive, use the <tt>mode</tt> attribute of <tt>&lt;tarfileset&gt;</tt>
 to set the permissions in the tar file, or &lt;apply&gt; the real tar program.
 to set the permissions in the tar file, or <code>&lt;apply&gt;</code> the real tar program.
 </li>
 <li> Ant is not symbolic link aware in moves, deletes and when recursing down a tree
 of directories to build up a list of files. Unexpected things can happen.
--- a/docs/manual/running.html
+++ b/docs/manual/running.html
@@ -405,7 +405,7 @@ org.apache.tools.ant.Executor implementation specified here.
 should not have any problems launching Ant form the Cygwin shell. It is important
 to note however, that once Ant is runing it is part of the JDK which operates as
 a native Windows application. The JDK is not a Cygwin executable, and it therefore
 has no knowledge of the Cygwin paths, etc. In particular when using the &lt;exec&gt;
 has no knowledge of the Cygwin paths, etc. In particular when using the <code>&lt;exec&gt;</code>
 task, executable names such as &quot;/bin/sh&quot; will not work, even though these
 work from the Cygwin shell from which Ant was launched. You can use an executable
 name such as &quot;sh&quot; and rely on that command being available in the Windows
--- a/docs/manual/tutorial-tasks-filesets-properties.html
+++ b/docs/manual/tutorial-tasks-filesets-properties.html
@@ -117,7 +117,7 @@ name. Otherwise a message is logged.</p>

 <p><i>(by the way: a short word to ants "namespaces" (don´t
 be confused with xml namespaces which will be also introduces in the future (1.6 or 1.7):
 an &lt;antcall&gt; creates a new space for property names. All properties from the caller
 an <code>&lt;antcall&gt;</code> creates a new space for property names. All properties from the caller
 are passed to the callee, but the callee can set its own properties without notice by the
 caller.)</i></p>

@@ -312,7 +312,7 @@ whithout being complex :-)</p>
 <p>The test case uses the ant property <i>ant.home</i> as reference. This property is set by the
 <tt>Launcher</tt> class which starts ant. We can use that property in our buildfiles as a
 <a href="using.html#built-in-props">build-in property [3]</a>. But if we create a new ant
 environment we have to set that value for our own. And we use the &lt;junit&gt; task in fork-mode.
 environment we have to set that value for our own. And we use the <code>&lt;junit&gt;</code> task in fork-mode.
 Therefore we have do modify our buildfile:
 <pre class="code">
    &lt;target name="junit" description="Runs the unit tests" depends="jar"&gt;
@@ -333,12 +333,12 @@ Therefore we have do modify our buildfile:
 <a name="path"/>
 <h2>Using nested paths</h2>
 <p>A task providing support for filesets is a very comfortable one. But there is another
 possibility of bundling files: the &lt;path&gt;. Fileset are easy if the files are all under
 possibility of bundling files: the <code>&lt;path&gt;</code>. Fileset are easy if the files are all under
 a common base directory. But if this is not the case you have a problem. Another disadvantage
 is its speed: if you have only a few files in a huge directory structure, why not use a
 &lt;filelist&gt; instead? &lt;path&gt;s combines these datatypes in that way that a path contains
 <code>&lt;filelist&gt;</code> instead? <code>&lt;path&gt;</code>s combines these datatypes in that way that a path contains
 other paths, filesets, dirsets and filelists. This is why <a href="http://ant-contrib.sourceforge.net/">
 Ant-Contribs [4]</a> &lt;foreach&gt; task is modified to support paths instead of filesets. So we want that,
 Ant-Contribs [4]</a> <code>&lt;foreach&gt;</code> task is modified to support paths instead of filesets. So we want that,
 too.</p>

 <p>Changing from fileset to path support is very easy:</p>
@@ -414,7 +414,7 @@ And would it be good to get all of them? - It depends on ...<p>

 <p>In this section we will extend that task to support returning a list of all files.
 Lists as property values are not supported by Ant natively. So we have to see how other
 tasks use lists. The most famous task using lists is Ant-Contribs &lt;foreach&gt;. All list
 tasks use lists. The most famous task using lists is Ant-Contribs <code>&lt;foreach&gt;</code>. All list
 elements are concatenated and separated with a customizable separator (default ',').</p>

 <p>So we do the following:</p>
@@ -799,8 +799,8 @@ failures of our own test (<b>//1 + 2</b>).</p>

 <p>And ... oh, all tests fail: <i>Ant could not find the task or a class this task relies upon.</i></p>

 <p>Ok: in the earlier steps we told Ant to use the Find class for the &lt;find&gt; task (remember the
 &lt;taskdef&gt; statement in the "use.init" target). But now we want to introduce that task as
 <p>Ok: in the earlier steps we told Ant to use the Find class for the <code>&lt;find&gt;</code> task (remember the
 <code>&lt;taskdef&gt;</code> statement in the "use.init" target). But now we want to introduce that task as
 a core task. And nobody wants to taskdef the javac, echo, ... So what to do? The answer is the
 src/main/.../taskdefs/default.properties. Here is the mapping between taskname and implementing
 class done. So we add a <tt>find=org.apache.tools.ant.taskdefs.Find</tt> as the last core
@@ -900,7 +900,7 @@ entry. For both we need some information:</p>
 <tr>
  <th>body</th>
  <td><i>more details about the path</i></td>
  <td>This new task looks inside a nested &lt;path/&gt; for occurrences of a file and stores
  <td>This new task looks inside a nested <code>&lt;path/&gt;</code> for occurrences of a file and stores
      all locations as a property. See the included manual for details.</td>
 </tr>
 <tr>
--- a/docs/manual/tutorial-writing-tasks.html
+++ b/docs/manual/tutorial-writing-tasks.html
@@ -64,7 +64,7 @@ So the buildfile contains three targets.
 </pre>

 This buildfile uses often the same value (src, classes, MyTask.jar), so we should rewrite that
 using &lt;property&gt;s. On second there are some handicaps: &lt;javac&gt; requires that the destination
 using <code>&lt;property&gt;</code>s. On second there are some handicaps: <code>&lt;javac&gt;</code> requires that the destination
 directory exists; a call of "clean" with a non existing classes directory will fail; "jar" requires
 the execution of some steps bofore. So the refactored code is:

@@ -118,7 +118,7 @@ its <i>depends</i>-clause the "compile" is executed before).
 <p>But after creating the jar we want to use our new Task. Therefore we need a
 new target "use". Before we can use our new task we have to declare it with
 <a href="http://ant.apache.org/manual/CoreTasks/taskdef.html" target="_blank">
 &lt;taskdef&gt; [2]</a>. And for easier process we change the default clause:
 <code>&lt;taskdef&gt;</code> [2]</a>. And for easier process we change the default clause:
 <pre class="code">
 &lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
 &lt;project name="MyTask" basedir="." default="<b>use</b>"&gt;
@@ -226,8 +226,8 @@ use:
 <a name="attributes">
 <h2>Attributes</h2>
 <p>Now we want to specify the text of our message (it seems that we are
 rewriting the &lt;echo/&gt; task :-). First we well do that with an attribute.
 It is very easy - for each attribute provide a <tt>public void set&lt;attributename&gt;(&lt;type&gt;
 rewriting the <code>&lt;echo/&gt;</code> task :-). First we well do that with an attribute.
 It is very easy - for each attribute provide a <tt>public void set<code>&lt;attributename&gt;</code>(<code>&lt;type&gt;</code>
 newValue)</tt> method and Ant will do the rest via reflection.</p>
 <pre class="code">
 import org.apache.tools.ant.Task;
@@ -281,7 +281,7 @@ would not set the message string to "${msg}" if there is a property "msg" with a

 <a name="NestedText"></a>
 <h2>Nested Text</h2>
 <p>Maybe you have used the &lt;echo&gt; task in a way like <tt>&lt;echo&gt;Hello World&lt;/echo&gt;</tt>.
 <p>Maybe you have used the <code>&lt;echo&gt;</code> task in a way like <tt>&lt;echo&gt;Hello World&lt;/echo&gt;</tt>.
 For that you have to provide a <tt>public void addText(String text)</tt> method.
 <pre class="code">
 ...
@@ -305,7 +305,7 @@ the <a href="http://ant.apache.org/manual/develop.html#nested-elements">Manual [
 We use the first way of the three described ways. There are several steps for that:<ol>
 <li>We create a class for collecting all the infos the nested element should contain.
  This class is created by the same rules for attributes and nested elements
  as for the task (set&lt;attributename&gt;() methods). </li>
  as for the task (<code>set&lt;attributename&gt;</code>() methods). </li>
 <li>The task holds multiple instances of this class in a list.</li>
 <li>A factory method instantiates an object, saves the reference in the list
  and returns it to Ant Core.</li>
@@ -580,8 +580,8 @@ target "test-jar" or you can download a nightly build from
 <a href="http://gump.covalent.net/jars/latest/ant/ant-testutil.jar">
 http://gump.covalent.net/jars/latest/ant/ant-testutil.jar [5]</a>.</p>

 <p>For executing the test and creating a report we need the optional tasks &lt;junit&gt;
 and &lt;junitreport&gt;. So we add to the buildfile:
 <p>For executing the test and creating a report we need the optional tasks <code>&lt;junit&gt;</code>
 and <code>&lt;junitreport&gt;</code>. So we add to the buildfile:
 <pre class="code">
 ...
 <font color="#9F9F9F">&lt;project name="MyTask" basedir="." </font>default="test"<font color="#9F9F9F">&gt;</font>