make sure each page of the Ant website says 'Apache Ant' at least once before it uses the shorter 'Ant'

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@1033999 13f79535-47bb-0310-9956-ffa450edef68
14 years ago · 6441f63978
--- a/docs/ant_in_anger.html
+++ b/docs/ant_in_anger.html
@@ -16,12 +16,12 @@
 -->
 <head>
 <title>
    Ant in Anger
    Apache Ant in Anger
 </title>
 </head>
 <body bgcolor="#FFFFFF" text="#000000">
 <h1 align="center">Ant in Anger:
 <h1 align="center">Apache Ant in Anger:
 </h1>
 <h2 align="center">
        Using Apache Ant in a Production Development System
--- a/docs/ant_task_guidelines.html
+++ b/docs/ant_task_guidelines.html
@@ -22,7 +22,7 @@ Apache Ant Task Design Guidelines
 <h1>Apache Ant Task Design Guidelines</h1>
 This document covers how to write Ant tasks to a standard required to be
 This document covers how to write Apache Ant tasks to a standard required to be
 incorporated into the Ant distribution. You may find it useful when
 writing tasks for personal use as the issues it addresses are still
 there in such a case.
--- a/docs/manual/Integration/jext-plugin.html
+++ b/docs/manual/Integration/jext-plugin.html
@@ -36,7 +36,7 @@ href="ftp://jext.sourceforge.net/pub/jext/plugins/AntWork.zip">ftp://jext.source
 <h2>Installation instructions from the Readme.txt:</h2>
 <p>You have to enable the Jext Console to see the Ant output (menu:
 <p>You have to enable the Jext Console to see the Apache Ant output (menu:
 Edit-&gt;Options... - General Panel), because the Ant messages are
 redirected to the Jext console.</p>
--- a/docs/manual/Tasks/ant.html
+++ b/docs/manual/Tasks/ant.html
@@ -27,7 +27,7 @@
 <h2><a name="ant">Ant</a></h2>
 <h3>Description</h3>
 <p>Runs Ant on a supplied buildfile. This can be used to build
 <p>Runs Apache Ant on a supplied buildfile. This can be used to build
 subprojects.  <strong>This task must not be used outside of a
 <code>target</code> if it invokes the same build file it is part
 of.</strong></p>
--- a/docs/manual/Tasks/antcall.html
+++ b/docs/manual/Tasks/antcall.html
@@ -88,7 +88,7 @@ behavior of this task is undefined.</p>
  </tr>
  <tr>
    <td valign="top">inheritAll</td>
    <td valign="top">If <code>true</code>, pass all properties to the new Ant
    <td valign="top">If <code>true</code>, pass all properties to the new Apache Ant
    project.  Defaults to <code>true</code>.
    </td>
    <td align="center" valign="top">No</td>
--- a/docs/manual/Tasks/antstructure.html
+++ b/docs/manual/Tasks/antstructure.html
@@ -27,7 +27,7 @@
 <h2><a name="antstructure">AntStructure</a></h2>
 <h3>Description</h3> 
 <p>Generates an DTD for Ant buildfiles which contains information
 <p>Generates an DTD for Apache Ant buildfiles which contains information
 about all tasks currently known to Ant.</p>
 <p>Actually the DTD will not be a real DTD for buildfiles since Ant's
--- a/docs/manual/Tasks/antversion.html
+++ b/docs/manual/Tasks/antversion.html
@@ -27,7 +27,7 @@
 <h2><a name="antversion">Antversion</a></h2>
 <h3>Description</h3>
 <p>
 Stores the Ant version (when used as task) or checks for a specific Ant version 
 Stores the Apache Ant version (when used as task) or checks for a specific Ant version 
 (when used as condition).
 <b>Since Ant 1.7.0</b>
 </p>
--- a/docs/manual/Tasks/apply.html
+++ b/docs/manual/Tasks/apply.html
@@ -29,7 +29,7 @@
 compatibility.</i></p>
 <h3>Description</h3>
 <p>Executes a system command. When the <i>os</i> attribute is specified, then
 the command is only executed when Ant is run on one of the specified operating
 the command is only executed when Apache Ant is run on one of the specified operating
 systems.</p>
 <p>The files and/or directories of a number of <a
--- a/docs/manual/Tasks/apt.html
+++ b/docs/manual/Tasks/apt.html
@@ -30,7 +30,7 @@
   In particular it is likely to be obsolete in JDK 6, which can run annotation
   processors as part of javac.
   If the &lt;apt&gt; task does break when upgrading JVM, please
   check to see if there is a more recent version of Ant that tracks
   check to see if there is a more recent version of Apache Ant that tracks
   any changes.</p>
--- a/docs/manual/Tasks/attrib.html
+++ b/docs/manual/Tasks/attrib.html
@@ -19,13 +19,13 @@
 <head>
 <meta http-equiv="Content-Language" content="en-us">
 <link rel="stylesheet" type="text/css" href="../stylesheets/style.css">
 <title>Ant User Manual</title>
 <title>Apache Ant User Manual</title>
 </head>
 <body>
 <h2><a name="attrib">Attrib</a></h2>
 <p><em>Since Ant 1.6.</em></p>
 <p><em>Since Apache Ant 1.6.</em></p>
 <h3>Description</h3>
 <p>Changes the attributes of a file or all files inside specified
--- a/docs/manual/Tasks/augment.html
+++ b/docs/manual/Tasks/augment.html
@@ -32,7 +32,7 @@ mapped as XML attributes. This is an unusual task that makes use of Ant's intern
 processing mechanisms to reload a previously declared reference by means of the 'id'
 attribute, then treats the declared <code>augment</code> element as though it were the
 original element.
 <b>Since Ant 1.8.1</b></p>
 <b>Since Apache Ant 1.8.1</b></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/bindtargets.html
+++ b/docs/manual/Tasks/bindtargets.html
@@ -55,7 +55,7 @@ This task basically avoid the creation of a target.
 it may not be used in a target. This is making the target dependency graph static
 and predictable as soon as every build file is loaded.</p>
 <p><b>Since Ant 1.8.2</b></p>
 <p><b>Since Apache Ant 1.8.2</b></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/ccm.html
+++ b/docs/manual/Tasks/ccm.html
@@ -33,7 +33,7 @@
  <li><a href="#ccmcreatetask">CCMCreateTask</a></li>
 </ul>
 <p>These ant tasks are wrappers around Continuus Source Manager. They have been tested
 <p>These Apache Ant tasks are wrappers around Continuus Source Manager. They have been tested
  against versions 5.1/6.2 on Windows 2000, but should work on other platforms with ccm installed.</p>
 <p>author: <a href="mailto:benoit.moussaud@criltelecom.com">Benoit Mousaud (benoit.moussaud@criltelecom.com) </a></p>
 <hr>
--- a/docs/manual/Tasks/changelog.html
+++ b/docs/manual/Tasks/changelog.html
@@ -45,7 +45,7 @@ operation may fail when using such an incompatible client.
  </tr>
  <tr>
    <td colspan="3">Attributes from parent Cvs task which are meaningful here<br>
    Since ant 1.6.1</td>
    Since Apache Ant 1.6.1</td>
  </tr>
  <tr>
    <td valign="top">cvsRoot</td>
--- a/docs/manual/Tasks/checksum.html
+++ b/docs/manual/Tasks/checksum.html
@@ -69,7 +69,7 @@ or set the <tt>fileext</tt> attribute.
    <td valign="top">The root directory where checksums should be written.</td>
    <td valign="top" align="center">No. If not specified, checksum files
      will be written to the same directory as the files themselves.
      <em>since Ant 1.6</em>
      <em>since Apache Ant 1.6</em>
    </td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/chgrp.html
+++ b/docs/manual/Tasks/chgrp.html
@@ -25,7 +25,7 @@
 <body>
 <h2><a name="Chgrp">Chgrp</a></h2>
 <p><em>Since Ant 1.6.</em></p>
 <p><em>Since Apache Ant 1.6.</em></p>
 <h3>Description</h3>
 <p>Changes the group of a file or all files inside specified
--- a/docs/manual/Tasks/chmod.html
+++ b/docs/manual/Tasks/chmod.html
@@ -37,7 +37,7 @@ write patterns.</p>
 href="../Types/fileset.html">FileSet</a> and supports all of
 FileSet's attributes and nested elements directly. More sets can be
 specified using nested <code>&lt;fileset&gt;</code> or
 <code>&lt;dirset&gt;</code> (<em>since Ant 1.6</em>) elements. </p>
 <code>&lt;dirset&gt;</code> (<em>since Apache Ant 1.6</em>) elements. </p>
 <p>Starting with Ant 1.6, this task also supports nested <a
 href="../Types/filelist.html">filelist</a>s.</p>
--- a/docs/manual/Tasks/chown.html
+++ b/docs/manual/Tasks/chown.html
@@ -25,7 +25,7 @@
 <body>
 <h2><a name="Chown">Chown</a></h2>
 <p><em>Since Ant 1.6.</em></p>
 <p><em>Since Apache Ant 1.6.</em></p>
 <h3>Description</h3>
 <p>Changes the owner of a file or all files inside specified
--- a/docs/manual/Tasks/clearcase.html
+++ b/docs/manual/Tasks/clearcase.html
@@ -23,7 +23,7 @@
 </head>
 <body>
 <h1>Ant ClearCase Tasks</h1>
 <h1>Apache Ant ClearCase Tasks</h1>
 <p>by:<br>
 Curtis White (cwhite at aracnet dot com),<br>
 Sean P. Kane (spkane at genomatica dot com),<br>
@@ -54,7 +54,7 @@ Sean Egan    (sean at cm-logic dot com)</p>
 <hr>
 <h2><a name="introduction">Introduction</a></h2>
 <p>Ant provides several optional tasks for working with ClearCase. These tasks correspond to various
 <p>Apache Ant provides several optional tasks for working with ClearCase. These tasks correspond to various
 ClearCase commands using the Cleartool program. The current tasks available for Ant correspond to only
 a few of the significant ClearCase commands.</p>
--- a/docs/manual/Tasks/componentdef.html
+++ b/docs/manual/Tasks/componentdef.html
@@ -42,7 +42,7 @@
      </li>
    </ol>
  <p>
    The purpose of this is to allow internal Ant definitions to be
    The purpose of this is to allow internal Apache Ant definitions to be
    made for tags like "and" or "or".
  </p>
--- a/docs/manual/Tasks/concat.html
+++ b/docs/manual/Tasks/concat.html
@@ -36,7 +36,7 @@
        list is empty and ignoreempty is true.
      </p>
      <p><strong>Since Ant 1.7.1</strong>, this task can be used as a
      <p><strong>Since Apache Ant 1.7.1</strong>, this task can be used as a
        <a href="../Types/resources.html#collection">Resource Collection</a>
        that will return exactly one 
        <a href="../Types/resources.html">resource</a>.
--- a/docs/manual/Tasks/condition.html
+++ b/docs/manual/Tasks/condition.html
@@ -57,7 +57,7 @@ you must specify exactly one condition.</p>
    <td valign="top">else</td>
    <td valign="top">The value to set the property to if the condition
      evaluates to <i>false</i>. By default the property will remain unset.
      <em>Since Ant 1.6.3</em>
      <em>Since Apache Ant 1.6.3</em>
    </td>
    <td valign="top" align="center">No</td>
  </tr>
--- a/docs/manual/Tasks/conditions.html
+++ b/docs/manual/Tasks/conditions.html
@@ -170,7 +170,7 @@ the tests succeed.
  <tr>
    <td valign="top">forcestring</td>
    <td valign="top">Force string comparison of <code>arg1/arg2</code>.
        Default is false.  <em>Since Ant 1.8.1</em>
        Default is false.  <em>Since Apache Ant 1.8.1</em>
    </td>
    <td valign="top" align="center">No</td>
  </tr>
--- a/docs/manual/Tasks/copy.html
+++ b/docs/manual/Tasks/copy.html
@@ -80,7 +80,7 @@ operation as <a href="../Types/filterset.html">filtersets</a>.
      specified in the <code>&lt;fileset&gt;</code>, or if the
      <code>file</code> attribute is also specified, then only
      <code>todir</code> is allowed.<br/>
      <em>Prior to Ant 1.8.2</em> the <code>tofile</code> attribute
      <em>Prior to Apache Ant 1.8.2</em> the <code>tofile</code> attribute
      only supported filesystem resources top copy from.</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/cvs.html
+++ b/docs/manual/Tasks/cvs.html
@@ -84,7 +84,7 @@ report 21657</a> for recommended workarounds.</p>
    <td valign="top">dest</td>
    <td valign="top">the directory where the checked out files should
    be placed.  Note that this is different from CVS's <code>-d</code> command line
    switch as Ant will never shorten pathnames to avoid empty
    switch as Apache Ant will never shorten pathnames to avoid empty
    directories.</td>
    <td align="center" valign="top">No, default is project's basedir.</td>
  </tr>
--- a/docs/manual/Tasks/cvstagdiff.html
+++ b/docs/manual/Tasks/cvstagdiff.html
@@ -72,7 +72,7 @@ operation may fail when using such an incompatible client.
  <tr>
    <td valign="top">ignoreRemoved</td>
    <td valign="top">When set to true, the report will not include any
      removed files.  <em>Since Ant 1.8.0</em></td>
      removed files.  <em>Since Apache Ant 1.8.0</em></td>
    <td align="center" valign="top">No, defaults to false.</td>
 </table>
@@ -101,7 +101,7 @@ operation may fail when using such an incompatible client.
  <tr>
    <td valign="top">package</td>
    <td valign="top">the package/module to analyze.<br>
    Since ant 1.6
    Since Ant 1.6
    multiple packages separated by spaces are possible.
    aliases corresponding to different modules are also possible
    Use a nested &lt;module&gt; element if you want to specify a module with
--- a/docs/manual/Tasks/cvsversion.html
+++ b/docs/manual/Tasks/cvsversion.html
@@ -28,7 +28,7 @@
 <h3>Description</h3>
 <p>
 This task allows to retrieve a CVS client and server version.
  <i>Since Ant 1.6.1.</i>
  <i>Since Apache Ant 1.6.1.</i>
 </p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/defaultexcludes.html
+++ b/docs/manual/Tasks/defaultexcludes.html
@@ -26,7 +26,7 @@
 <h2><a name="echo">DefaultExcludes</a></h2>
 <p><em>since Ant 1.6</em></p>
 <p><em>since Apache Ant 1.6</em></p>
 <h3>Description</h3>
 <p>Alters the default excludes for all subsequent processing in the
--- a/docs/manual/Tasks/delete.html
+++ b/docs/manual/Tasks/delete.html
@@ -89,7 +89,7 @@ in <strong>Directory-based Tasks</strong>, and see the
  <tr>
    <td valign="top">quiet</td>
    <td valign="top">If the specified file or directory does not exist,
     do not display a diagnostic message (unless Ant
     do not display a diagnostic message (unless Apache Ant
     has been invoked with the <code>-verbose</code> or
     <code>-debug</code> switches) or modify the exit status to
     reflect an error.
--- a/docs/manual/Tasks/dependset.html
+++ b/docs/manual/Tasks/dependset.html
@@ -79,7 +79,7 @@ well as other stylesheets imported by the main stylesheet.
 <p>The <code>&lt;sources&gt;</code> element is a
 <a href="../Types/resources.html#union">Union</a> into which
 arbitrary resource collections can be nested. <b>Since Ant 1.7</b>
 arbitrary resource collections can be nested. <b>Since Apache Ant 1.7</b>
 </p>
 <h4>srcfileset</h4>
--- a/docs/manual/Tasks/diagnostics.html
+++ b/docs/manual/Tasks/diagnostics.html
@@ -27,7 +27,7 @@
 <h2><a name="diagnostics">Diagnostics</a></h2>
 <h3>Diagnostics</h3>
 <p>
 Runs Ant's <code>-diagnostics</code> code inside Ant itself. This is good for 
 Runs Apache Ant's <code>-diagnostics</code> code inside Ant itself. This is good for 
 debugging Ant's configuration under an IDE. 
 <b>Since Ant 1.7.0</b>
 </p>
--- a/docs/manual/Tasks/ear.html
+++ b/docs/manual/Tasks/ear.html
@@ -74,7 +74,7 @@ to a value other than its default, <code>&quot;add&quot;</code>.</b></p>
    <td valign="top">For entries coming from existing archives (like
    nested <em>zipfileset</em>s or while updating the archive), keep
    the compression as it has been originally instead of using the
    <em>compress</em> attribute.  Defaults false.  <em>Since Ant
    <em>compress</em> attribute.  Defaults false.  <em>Since Apache Ant
    1.6</em></td>
    <td align="center" valign="top">No</td>
  </tr>
--- a/docs/manual/Tasks/echo.html
+++ b/docs/manual/Tasks/echo.html
@@ -57,7 +57,7 @@ ignored</p>
    <td valign="top">output</td>
    <td valign="top">the <a href="../Types/resources.html">Resource</a>
      to write the message to (see <a href="../develop.html#set-magic">note</a>).
      <b>Since Ant 1.8</b></td>
      <b>Since Apache Ant 1.8</b></td>
  </tr>
  <tr>
    <td valign="top">append</td>
--- a/docs/manual/Tasks/echoproperties.html
+++ b/docs/manual/Tasks/echoproperties.html
@@ -46,7 +46,7 @@ files.</p>
    <td valign="top">If specified, the value indicates the name of the
    file to send the output of the statement to.  The generated output file
    is compatible for loading by any Java application as a property file.
    If not specified, then the output will go to the Ant log.</td>
    If not specified, then the output will go to the Apache Ant log.</td>
    <td valign="top" align="center">No</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/echoxml.html
+++ b/docs/manual/Tasks/echoxml.html
@@ -26,7 +26,7 @@
 <h2>EchoXML</h2>
 <h3>Description</h3>
 <p>Echo nested XML to the console or a file. <b>Since Ant 1.7</b></p>
 <p>Echo nested XML to the console or a file. <b>Since Apache Ant 1.7</b></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
--- a/docs/manual/Tasks/ejb.html
+++ b/docs/manual/Tasks/ejb.html
@@ -25,7 +25,7 @@
 <body>
 <h1>Ant EJB Tasks User Manual</h1>
 <h1>Apache Ant EJB Tasks User Manual</h1>
 <p>by</p>
 <!-- Names are in alphabetical order, on last name -->
 <ul>
--- a/docs/manual/Tasks/exec.html
+++ b/docs/manual/Tasks/exec.html
@@ -27,7 +27,7 @@
 <h2><a name="exec">Exec</a></h2>
 <h3>Description</h3>
 <p>Executes a system command. When the <i>os</i> attribute is specified, then
 the command is only executed when Ant is run on one of the specified operating
 the command is only executed when Apache Ant is run on one of the specified operating
 systems.</p>
 <p>Note that you cannot interact with the forked program, the only way
--- a/docs/manual/Tasks/fail.html
+++ b/docs/manual/Tasks/fail.html
@@ -58,7 +58,7 @@ or character data nested into the element.</p>
    <td valign="top">status</td>
    <td valign="top">Exit using the specified status code;
      assuming the generated Exception is not caught, the
      JVM will exit with this status. <em>Since Ant 1.6.2</em></td>
      JVM will exit with this status. <em>Since Apache Ant 1.6.2</em></td>
    <td align="center" valign="top">No</td>
  </tr>
 </table>
--- a/docs/manual/Tasks/fixcrlf.html
+++ b/docs/manual/Tasks/fixcrlf.html
@@ -62,7 +62,7 @@
  </p>
  <p>
    Since <b>Ant 1.7</b>, this task can be used in a
    Since <b>Apache Ant 1.7</b>, this task can be used in a
    <a href="../Types/filterchain.html">filterchain</a>.
  </p>
--- a/docs/manual/Tasks/ftp.html
+++ b/docs/manual/Tasks/ftp.html
@@ -29,7 +29,7 @@
 <p>The ftp task implements a basic FTP client that can send, receive,
 list, delete files, and create directories.  See below for descriptions and examples of how
 to perform each task.</p>
 <p><b>Note:</b> This task depends on external libraries not included in the Ant distribution.
 <p><b>Note:</b> This task depends on external libraries not included in the Apache Ant distribution.
 See <a href="../install.html#commons-net">Library Dependencies</a> for more information.
 <i>Get the latest version of this library, for the best support in Ant</i>
--- a/docs/manual/Tasks/get.html
+++ b/docs/manual/Tasks/get.html
@@ -39,7 +39,7 @@ A username and password can be specified, in which case basic 'slightly encoded
 plain text' authentication is used. This is only secure over an HTTPS link.
 </p>
 <p><b>Proxies</b>. Since Ant 1.7.0, Ant running on Java1.5 or later can
 <p><b>Proxies</b>. Since Apache Ant 1.7.0, Ant running on Java1.5 or later can
  <a href="../proxy.html">use the proxy settings of the operating
    system</a> if enabled with the
  <code>-autoproxy</code> option. There is also the
--- a/docs/manual/Tasks/image.html
+++ b/docs/manual/Tasks/image.html
@@ -201,7 +201,7 @@ nested inside the Draw object.</p>
 </table>
 <h4>mapper</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p><em>Since Apache Ant 1.8.0</em></p>
 <p>You can define filename transformations by using a
  nested <a href="../Types/mapper.html">mapper</a> element. The
--- a/docs/manual/Tasks/import.html
+++ b/docs/manual/Tasks/import.html
@@ -38,7 +38,7 @@
  <p>
    <b>Note</b> as seen above, this task heavily relies on the ProjectHelper
    implementation and doesn't really perform any work of its own.  If
    you have configured Ant to use a ProjectHelper other than Ant's
    you have configured Apache Ant to use a ProjectHelper other than Ant's
    default, this task may or may not work.
  </p>
--- a/docs/manual/Tasks/include.html
+++ b/docs/manual/Tasks/include.html
@@ -28,7 +28,7 @@
    Include another build file into the current project.
  </p>
  <p><em>since Ant 1.8.0</em></p>
  <p><em>since Apache Ant 1.8.0</em></p>
  <p>
    <b>Note</b> this task heavily relies on the ProjectHelper
--- a/docs/manual/Tasks/input.html
+++ b/docs/manual/Tasks/input.html
@@ -42,7 +42,7 @@ one of the predefined.</p>
 user. This property can then be used during the following build
 run. Input behaves according to <a href="property.html">property
 task</a> which means that existing properties cannot be overriden.
 Since Ant 1.6, <code>&lt;input&gt;</code> will not prompt for input if
 Since Apache Ant 1.6, <code>&lt;input&gt;</code> will not prompt for input if
 a property should be set by the task that has already been set in the
 project (and the task wouldn't have any effect).</p>
--- a/docs/manual/Tasks/jar.html
+++ b/docs/manual/Tasks/jar.html
@@ -48,7 +48,7 @@ multiple ones to merge together different trees of files into one JAR.
 The extended fileset and groupfileset child elements from the zip task are
 also available in the jar task.
 See the <a href="zip.html">Zip</a> task for more details and examples.</p>
 <p>If the manifest is omitted, a simple one will be supplied by Ant.</p>
 <p>If the manifest is omitted, a simple one will be supplied by Apache Ant.</p>
 <p>The <code>update</code> parameter controls what happens if the JAR
 file already exists. When set to <code>yes</code>, the JAR file is
--- a/docs/manual/Tasks/jarlib-resolve.html
+++ b/docs/manual/Tasks/jarlib-resolve.html
@@ -119,7 +119,7 @@ http://download.oracle.com/javase/1.3/docs/guide/extensions/versioning.html
 </table>
 <h4>ant</h4>
 <p>The ant resolver allows you to run a ant build file to generate a library.</p>
 <p>The ant resolver allows you to run an Apache Ant build file to generate a library.</p>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
    <td valign="top"><b>Attribute</b></td>
--- a/docs/manual/Tasks/java.html
+++ b/docs/manual/Tasks/java.html
@@ -26,7 +26,7 @@
 <h2><a name="java">Java</a></h2>
 <h3>Description</h3>
 <p>Executes a Java class within the running (Ant) VM or forks another VM if
 <p>Executes a Java class within the running (Apache Ant) VM or forks another VM if
 specified.</p>
 <p>
 If odd things go wrong when you run this task, set fork="true" to use a new
--- a/docs/manual/Tasks/javac.html
+++ b/docs/manual/Tasks/javac.html
@@ -32,7 +32,7 @@ source files to compile. Only Java files that have no corresponding
 <code>.class</code> file
 or where the class file is older than the
 <code>.java</code> file will be compiled.</p>
 <p>Note: Ant uses only the names of the source and class files to find
 <p>Note: Apache Ant uses only the names of the source and class files to find
 the classes that need a rebuild. It will not scan the source and therefore
 will have no knowledge about nested classes, classes that are named different
 from the source file, and so on. See the
--- a/docs/manual/Tasks/javacc.html
+++ b/docs/manual/Tasks/javacc.html
@@ -33,7 +33,7 @@
 <p>
  To use the javacc task, set the <i>target</i> attribute to the name of the
  grammar file to process.  You also need to specify the directory containing
  the JavaCC installation using the <i>javacchome</i> attribute, so that ant
  the JavaCC installation using the <i>javacchome</i> attribute, so that Apache Ant
  can find the JavaCC classes.  Optionally, you can also set the
  <i>outputdirectory</i> to write the generated file to a specific directory.
  Otherwise javacc writes the generated files to the directory containing
--- a/docs/manual/Tasks/javadoc.html
+++ b/docs/manual/Tasks/javadoc.html
@@ -36,7 +36,7 @@ and management costs over time. This task, however, has no notion of
 all packages will be processed each time this task is run. In general, however,
 this task is used much less frequently.</p>
 <p>NOTE: since javadoc calls System.exit(), javadoc cannot be run inside the
 same VM as Ant without breaking functionality. For this reason, this task
 same VM as Apache Ant without breaking functionality. For this reason, this task
 always forks the VM. This overhead is not significant since javadoc is normally a heavy
 application and will be called infrequently.</p>
 <p>NOTE: the packagelist attribute allows you to specify the list of packages to
--- a/docs/manual/Tasks/javah.html
+++ b/docs/manual/Tasks/javah.html
@@ -42,7 +42,7 @@ name="implementationvalues">Here are the choices of the attribute</a>:</p>
  <li>kaffeh (the native standard compiler of <a href="http://www.kaffe.org" target="_top">Kaffe</a>)</li>
  <li>gcjh (the native standard compiler
  of <a href="http://gcc.gnu.org/java/"
  target="_top">gcj and gij</a>) <em>since Ant 1.8.2</em></li>
  target="_top">gcj and gij</a>) <em>since Apache Ant 1.8.2</em></li>
 </ul>
 <p><b>Note:</b> if you are using this task to work on multiple files
--- a/docs/manual/Tasks/jdepend.html
+++ b/docs/manual/Tasks/jdepend.html
@@ -91,7 +91,7 @@ href="#nested">nested elements</a>.</p>
  <tr>
    <td VALIGN=TOP>includeruntime</td>
    <td VALIGN=TOP>Implicitly add the classes required to run jdepend
    in forked mode. (Ignored if fork is disabled). Since ant 1.6.</td>
    in forked mode. (Ignored if fork is disabled). Since Apache Ant 1.6.</td>
    <td ALIGN=CENTER VALIGN=TOP>No, default is "no".</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/jjdoc.html
+++ b/docs/manual/Tasks/jjdoc.html
@@ -26,7 +26,7 @@
 <h2>
 <a NAME="jjtree"></a>JJDoc</h2>
 <p><em>Since Ant 1.6</em></p>
 <p><em>Since Apache Ant 1.6</em></p>
 <h3>Description</h3>
 <p>Invokes the <a href="http://javacc.dev.java.net/">JJDoc</a> preprocessor
--- a/docs/manual/Tasks/jjtree.html
+++ b/docs/manual/Tasks/jjtree.html
@@ -36,7 +36,7 @@ JJTree is run through JavaCC to create the parser.
 <p>To use the jjtree task, set the <i>target</i> attribute to the name
 of the JJTree grammar file to process. You also need to specify the directory
 containing the JavaCC installation using the <i>javacchome</i> attribute,
 so that ant can find the JavaCC classes. Optionally, you can also set the
 so that Ant can find the JavaCC classes. Optionally, you can also set the
 <i>outputdirectory</i>
 to write the generated JavaCC grammar and node files to a specific directory.
 Otherwise jjtree writes the generated JavaCC grammar and node files to the directory
@@ -535,7 +535,7 @@ is set to true when invoking JJTree.
 </table>
 <p>*) <u>Footnote</u>: When running JJTree with the Ant taskdef <i>jjtree</i> the option <code>-OUTPUT_DIRECTORY</code> must always 
 be set, because the project's basedir and the ant working directory might differ. So even if you don't specify the jjtree taskdef 
 be set, because the project's basedir and the Ant working directory might differ. So even if you don't specify the jjtree taskdef 
 <i>outputdirectory</i> JJTree will be called with the <code>-OUTPUT_DIRECTORY</code> set to the project's basedirectory. 
 But when the <code>-OUTPUT_DIRECTORY</code> is set, the <code>-OUTPUT_FILE</code> setting is handled as if relative to this 
 <code>-OUTPUT_DIRECTORY</code>. Thus when the <code>-OUTPUT_FILE</code> is absolute or contains a drive letter we have a 
--- a/docs/manual/Tasks/jspc.html
+++ b/docs/manual/Tasks/jspc.html
@@ -27,7 +27,7 @@
 <h2><a name="jspc">jspc (deprecated)</a></h2>
 <h3>Description</h3>
 <p> Ant task to run the JSP compiler and turn JSP pages into Java source.
 <p> Apache Ant task to run the JSP compiler and turn JSP pages into Java source.
 <p><b>Deprecated</b> if you use this task with Tomcat's Jasper JSP
 compiler, you should seriously consider using the task shipping with
--- a/docs/manual/Tasks/junit.html
+++ b/docs/manual/Tasks/junit.html
@@ -31,7 +31,7 @@ This task has been tested with JUnit 3.0 up to JUnit 3.8.2; it won't
 work with versions prior to JUnit 3.0. It also works with JUnit 4.0, including
 "pure" JUnit 4 tests using only annotations and no <code>JUnit4TestAdapter</code>.</p>
 <p><strong>Note:</strong> This task depends on external libraries not included
 in the Ant distribution.  See <a href="../install.html#librarydependencies">
 in the Apache Ant distribution.  See <a href="../install.html#librarydependencies">
 Library Dependencies</a> for more information.
 </p>
 <p>
--- a/docs/manual/Tasks/junitreport.html
+++ b/docs/manual/Tasks/junitreport.html
@@ -27,7 +27,7 @@ Merge the individual XML files generated by the JUnit task and eventually apply
 a stylesheet on the resulting merged document to provide a browsable report of
 the testcases results.
 <p><strong>Note:</strong> This task depends on external libraries not included in
 the Ant distribution.  See <a href="../install.html#librarydependencies">
 the Apache Ant distribution.  See <a href="../install.html#librarydependencies">
 Library Dependencies</a> for more information.</p>
 <h3>Requirements</h3>
--- a/docs/manual/Tasks/length.html
+++ b/docs/manual/Tasks/length.html
@@ -29,7 +29,7 @@
 <p>Display or set a property containing length information for
   a string, a file, or one or more nested
   <a href="../Types/resources.html#collection">Resource Collection</a>s.
   Can also be used as a condition. <b>Since Ant 1.6.3</b></p>
   Can also be used as a condition. <b>Since Apache Ant 1.6.3</b></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
--- a/docs/manual/Tasks/loadfile.html
+++ b/docs/manual/Tasks/loadfile.html
@@ -64,7 +64,7 @@ the property is not set.</p>
  </tr>
  <tr>
    <td valign="top">quiet</td>
    <td valign="top">Do not display a diagnostic message (unless Ant has been 
    <td valign="top">Do not display a diagnostic message (unless Apache Ant has been 
    invoked with the <code>-verbose</code> or <code>-debug</code>
    switches) or modify the exit status to reflect an error. Setting this to 
    "true" implies setting failonerror to "false".
--- a/docs/manual/Tasks/loadproperties.html
+++ b/docs/manual/Tasks/loadproperties.html
@@ -26,7 +26,7 @@
 <h2><a name="loadproperties">LoadProperties</a></h2>
 <h3>Description</h3>
 <p>
 Load a file's contents as Ant properties.  This is equivalent
 Load a file's contents as Apache Ant properties.  This is equivalent
 to <code>&lt;property file|resource=&quot;...&quot;/&gt;</code> except that it
 supports nested <code>&lt;filterchain&gt;</code> elements.
 Also if the file is missing, the build is halted with an error, rather
--- a/docs/manual/Tasks/loadresource.html
+++ b/docs/manual/Tasks/loadresource.html
@@ -25,7 +25,7 @@
 <h2><a name="loadresource">LoadResource</a></h2>
 <p><em>Since Ant 1.7</em></p>
 <p><em>Since Apache Ant 1.7</em></p>
 <h3>Description</h3>
 <p>
--- a/docs/manual/Tasks/local.html
+++ b/docs/manual/Tasks/local.html
@@ -26,7 +26,7 @@
 <h2>Local</h2>
 <h3>Description</h3>
 <p>Adds a local property to the current scope. Property scopes exist at Ant's
 <p>Adds a local property to the current scope. Property scopes exist at Apache Ant's
 various "block" levels. These include targets as well as the
 <a href="parallel.html">Parallel</a> and <a href="sequential.html">Sequential</a>
 task containers (including <a href="macrodef.html">Macrodef</a> bodies). A local
--- a/docs/manual/Tasks/macrodef.html
+++ b/docs/manual/Tasks/macrodef.html
@@ -39,7 +39,7 @@
      other attributes. See the examples.
    </p>
    <p>
      <em>since Ant 1.6</em>
      <em>since Apache Ant 1.6</em>
    </p>
    <h3>Parameters</h3>
    <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/mail.html
+++ b/docs/manual/Tasks/mail.html
@@ -42,7 +42,7 @@
    href="../using.html#path">path-like structures</a>.  This means
    any filesystem based <a
    href="../Types/resources.html">resource</a> or resource
    collection can be used to point to attachments.  Prior to Ant 1.7
    collection can be used to point to attachments.  Prior to Apache Ant 1.7
    only <code>&lt;fileset&gt;</code> has been supported as a nested
    element, you can still use this directly without an
    <code>&lt;attachments&gt;</code> container.
--- a/docs/manual/Tasks/manifest.html
+++ b/docs/manual/Tasks/manifest.html
@@ -42,7 +42,7 @@ greater than 72 bytes being wrapped and continued on the next
 line.</p>
 <p>
  The Ant team regularly gets complaints that this task in generating invalid
  The Apache Ant team regularly gets complaints that this task in generating invalid
  manifests. By and large, this is not the case: we believe that we are following
  the specification to the letter. The usual problem is that some third party
  manifest reader is not following the same specification as well as they think
--- a/docs/manual/Tasks/manifestclasspath.html
+++ b/docs/manual/Tasks/manifestclasspath.html
@@ -46,7 +46,7 @@ it silently ignores entries for which it cannot find any corresponding file.</p>
 specification by the <code>&lt;manifest&gt;</code> element, where the
 defined property is re-referenced.</p>
 <p><em>since Ant 1.7</em></p>
 <p><em>since Apache Ant 1.7</em></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/move.html
+++ b/docs/manual/Tasks/move.html
@@ -37,7 +37,7 @@ Collection</a>s are used to select a group of files to move.  Only
 file system based resource collections are supported, this includes <a
 href="../Types/fileset.html">fileset</a>s, <a
 href="../Types/filelist.html">filelist</a> and <a
 href="../using.html#path">path</a>.  Prior to Ant 1.7 only
 href="../using.html#path">path</a>.  Prior to Apache Ant 1.7 only
 <code>&lt;fileset&gt;</code> has been supported as a nested element.
 To use a resource collection, the <code>todir</code> attribute must be
 set.</p>
--- a/docs/manual/Tasks/native2ascii.html
+++ b/docs/manual/Tasks/native2ascii.html
@@ -183,7 +183,7 @@ only if a given converter implementation will be used.</p>
  </tr>
 </table>
 <h4>implementationclasspath <em>since Ant 1.8.0</em></h4>
 <h4>implementationclasspath <em>since Apache Ant 1.8.0</em></h4>
 <p>A <a href="../using.html#path">PATH like structure</a> holding the
  classpath to use when loading the converter implementation if a
--- a/docs/manual/Tasks/netrexxc.html
+++ b/docs/manual/Tasks/netrexxc.html
@@ -27,7 +27,7 @@
 <h2><a name="netrexxc">NetRexxC</a></h2>
 <h3>Description</h3>
 <p>Compiles a <a href="http://www2.hursley.ibm.com/netrexx" target="_top">NetRexx</a>
 source tree within the running (Ant) VM.</p>
 source tree within the running (Apache Ant) VM.</p>
 <p>The source and destination directory will be recursively scanned for
 NetRexx source files to compile.  Only NetRexx files that have no corresponding
 class file or where the class file is older than the java file will be compiled.</p>
--- a/docs/manual/Tasks/pack.html
+++ b/docs/manual/Tasks/pack.html
@@ -54,7 +54,7 @@ resource is newer.</p>
 <h4>any <a href="../Types/resources.html">resource</a> or single element
 resource collection</h4>
 <p>The specified resource will be used as src. <em>Since Ant 1.7</em></p>
 <p>The specified resource will be used as src. <em>Since Apache Ant 1.7</em></p>
 <h3>Examples</h3>
 <blockquote><pre>
--- a/docs/manual/Tasks/parallel.html
+++ b/docs/manual/Tasks/parallel.html
@@ -31,7 +31,7 @@
    Every task will run in its own thread, with the likelihood of 
    concurrency problems scaling with the number of CPUs on the host system.
 </p>
 <p><b>Warning:</b> While the Ant core is believed to be thread safe, no such 
 <p><b>Warning:</b> While the Apache Ant core is believed to be thread safe, no such 
    guarantees are made about tasks, which are not tested for thread safety during
    Ant's test process. 
    Third party tasks may or may not be thread safe, and some of Ant's core tasks, such as
--- a/docs/manual/Tasks/patch.html
+++ b/docs/manual/Tasks/patch.html
@@ -49,7 +49,7 @@
  <tr>
    <td valign="top">destfile</td> 
    <td valign="top">the file to send the output to instead of
      patching the file(s) in place.  <em>since Ant 1.6</em></td>
      patching the file(s) in place.  <em>since Apache Ant 1.6</em></td>
    <td align="center" valign="top">No.</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/pathconvert.html
+++ b/docs/manual/Tasks/pathconvert.html
@@ -38,7 +38,7 @@ of files in a FileList into a path.
 drive letters to Unix paths, and vice-versa.</p>
 <p>More complex transformations can be achieved using a nested
 <a href="../Types/mapper.html"><code>&lt;mapper&gt;</code></a>
 (since Ant 1.6.2).
 (since Apache Ant 1.6.2).
 </p>
 <h3>Parameters</h3>
--- a/docs/manual/Tasks/perforce.html
+++ b/docs/manual/Tasks/perforce.html
@@ -39,7 +39,7 @@
 <h2><a name="intro">Introduction</a></h2>
 <p>These tasks provide an interface to the <a href="http://www.perforce.com" target="_top">Perforce</a> SCM.
 The <code>org.apache.tools.ant.taskdefs.optional.perforce</code> package consists of a simple framework to support 
 p4 functionality as well as some Ant tasks encapsulating frequently used (by me :-) p4 commands. 
 p4 functionality as well as some Apache Ant tasks encapsulating frequently used (by me :-) p4 commands. 
 However, the addition of new p4 commands is a pretty simple task (see the source). 
 Although it is possible to use these commands on the desktop, 
 they were primarily intended to be used by automated build systems.</p>
@@ -355,14 +355,14 @@ is not the latest any more.
    <td valign="top">changeproperty</td>
    <td valign="top">Name of a property to which the new change number
    will be assigned if the Perforce server renumbers the change<br>
    Since ant 1.6.1</td>
    Since Ant 1.6.1</td>
    <td valign="top" align="center">No</td>
  </tr>
  <tr>
    <td valign="top">needsresolveproperty</td>
    <td valign="top">Name of property which will be set to <code>true</code>
    if the submit requires a resolve<br>
    Since ant 1.6.1</td>
    Since Ant 1.6.1</td>
    <td valign="top" align="center">No</td>
  </tr>
 </table>
@@ -996,7 +996,7 @@ P4Resolve does not use a change list number (it takes it from the files it is wo
 </tr>
 <tr>
    <td valign="top">Jan 2004</td>
    <td valign="top">ant 1.6.1</td>
    <td valign="top">Ant 1.6.1</td>
    <td valign="top">
 Changed p4submit, needsresolveproperty and changeproperty added</td>
 </tr>
--- a/docs/manual/Tasks/presetdef.html
+++ b/docs/manual/Tasks/presetdef.html
@@ -37,7 +37,7 @@
      or elements preset.
    </p>
    <p>
      <em>since Ant 1.6</em>
      <em>since Apache Ant 1.6</em>
    </p>
    <p>
      The resolution of properties in any of the attributes or
--- a/docs/manual/Tasks/projecthelper.html
+++ b/docs/manual/Tasks/projecthelper.html
@@ -32,7 +32,7 @@ ProjectHelper at runtime.
 <p>The helpers will be added after all the already registered helpers, but before
 the default one (ProjectHelper2)
 </p>
 <p>See the description of Ant's
 <p>See the description of Apache Ant's
 <a href="../projecthelper.html">Project Helper</a> for more information.
 </p>
 <p><b>Since Ant 1.8.2</b></p>
--- a/docs/manual/Tasks/property.html
+++ b/docs/manual/Tasks/property.html
@@ -58,7 +58,7 @@ properties. These references are resolved at the time these properties are set.
 This also holds for properties loaded from a property file.</p>
 <p>A list of predefined properties can be found <a
 href="../properties.html#built-in-props">here</a>.</p>
 <p>Since Ant 1.7.1 it is possible to load properties defined in xml
 <p>Since Apache Ant 1.7.1 it is possible to load properties defined in xml
 according to <a href="http://java.sun.com/dtd/properties.dtd">Suns DTD</a>,
 if Java5+ is present. For this the name of the file, resource or url has 
 to end with <tt>.xml</tt>.</p>
--- a/docs/manual/Tasks/propertyfile.html
+++ b/docs/manual/Tasks/propertyfile.html
@@ -27,7 +27,7 @@
 <hr>
 <h2><a name="introduction">Introduction</a></h2>
 <p>Ant provides an optional task for editing property files. This is
 <p>Apache Ant provides an optional task for editing property files. This is
 very useful when wanting to make unattended modifications to
 configuration files for application servers and
 applications. Currently, the task maintains a working property file
--- a/docs/manual/Tasks/propertyhelper.html
+++ b/docs/manual/Tasks/propertyhelper.html
@@ -29,7 +29,7 @@
 <p>This task is provided for the purpose of allowing the user to
 <b>(a)</b> install a different PropertyHelper at runtime, or
 <b>(b)</b> (hopefully more often) install one or more PropertyHelper Delegates into the
 PropertyHelper active on the current Project. This is somewhat advanced Ant usage and
 PropertyHelper active on the current Project. This is somewhat advanced Apache Ant usage and
 assumes a working familiarity with the modern Ant APIs. See the description of Ant's
 <a href="../properties.html#propertyHelper">Property Helper</a> for more information.
 <b>Since Ant 1.8.0</b></p>
--- a/docs/manual/Tasks/pvcstask.html
+++ b/docs/manual/Tasks/pvcstask.html
@@ -25,10 +25,10 @@
 <body>
 <h1>
 Ant Pvcs Task User Manual</h1>
 Apache Ant Pvcs Task User Manual</h1>
 <p><b>Note:</b>
 Before using this task, the user running ant must have access to the
 Before using this task, the user running Ant must have access to the
 commands of PVCS (get and pcli) and must have access to the
 repository. Note that the way to specify the repository is platform
 dependent so use property to specify location of repository.
@@ -56,7 +56,7 @@ Table of Contents</h2>
 <hr>
 <h2><a NAME="introduction">Introduction</a></h2>
 The pvcs task allows the user of ant to extract the latest edition
 The pvcs task allows the user of Ant to extract the latest edition
 of the source code from a PVCS repository. PVCS is a version control system
 developed by <a href="http://www.merant.com/products/pvcs">Merant</a>.
 <br>
@@ -122,7 +122,7 @@ promotion group and with that label to be extracted.
 <td VALIGN=TOP WIDTH="12%">config</td>
 <td VALIGN=TOP WIDTH="78%">path of a non default .cfg file.
 Can be given absolute or relative to ant's base directory.
 Can be given absolute or relative to Ant's base directory.
 </td>
 <td VALIGN=TOP WIDTH="10%">No</td>
--- a/docs/manual/Tasks/recorder.html
+++ b/docs/manual/Tasks/recorder.html
@@ -72,7 +72,7 @@ a buildFinished event.</p>
  </tr>
  <tr>
    <td valign="top">emacsmode</td>
    <td valign="top">Removes <code>[task]</code> banners like Ant's
    <td valign="top">Removes <code>[task]</code> banners like Apache Ant's
    <code>-emacs</code> command line switch if set to
    <em>true</em>.</td>
    <td align="center" valign="middle">no, default is <em>false</em></td>
--- a/docs/manual/Tasks/replace.html
+++ b/docs/manual/Tasks/replace.html
@@ -123,7 +123,7 @@ have been regenerated by this task.</p>
  <tr>
    <td valign="top">preserveLastModified</td>
    <td valign="top">Keep the file timestamp(s) even if the file(s)
      is(are) modified.  <em>since Ant 1.8.0.</em></td>
      is(are) modified.  <em>since Apache Ant 1.8.0.</em></td>
    <td valign="top" align="center">No, defaults to false</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/replaceregexp.html
+++ b/docs/manual/Tasks/replaceregexp.html
@@ -84,7 +84,7 @@ See details in the documentation of the <a href="../Types/regexp.html#implementa
  </tr>
  <tr>
    <td valign="top">encoding</td>
    <td valign="top">The encoding of the file. <em>since Ant 1.6</em></td>
    <td valign="top">The encoding of the file. <em>since Apache Ant 1.6</em></td>
    <td align="center">No - defaults to default JVM encoding</td>
  </tr>
  <tr>
--- a/docs/manual/Tasks/resourcecount.html
+++ b/docs/manual/Tasks/resourcecount.html
@@ -29,7 +29,7 @@
 <h3>Description</h3>
 <p>Display or set a property containing the size of a nested
   <a href="../Types/resources.html#collection">Resource Collection</a>.
   Can also be used as a condition. <b>Since Ant 1.7</b></p>
   Can also be used as a condition. <b>Since Apache Ant 1.7</b></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
  <tr>
--- a/docs/manual/Tasks/retry.html
+++ b/docs/manual/Tasks/retry.html
@@ -26,7 +26,7 @@
 <h3>Description</h3>
 <p>Retry is a container which executes a single nested task until either: there is no failure; or:
 its <em>retrycount</em> has been exceeded. If this happens a BuildException is thrown.
 <em>Since Ant 1.7.1</em></p>
 <em>Since Apache Ant 1.7.1</em></p>
 <h3>Parameters</h3>
 <table border="1" cellpadding="2" cellspacing="0">
--- a/docs/manual/Tasks/rexec.html
+++ b/docs/manual/Tasks/rexec.html
@@ -30,7 +30,7 @@ Task to automate a remote rexec session. Just like the Telnet task,
 it uses nested <tt>&lt;read&gt;</tt> to indicate strings to wait for, and
 <tt>&lt;write&gt;</tt> tags to specify text to send to the remote process.
 <p><b>Note:</b> This task depends on external libraries not included in the Ant distribution.
 <p><b>Note:</b> This task depends on external libraries not included in the Apache Ant distribution.
 See <a href="../install.html#librarydependencies">Library Dependencies</a> for more information.</p>
 <p>You can specify the commands you want to execute as nested elements
--- a/docs/manual/Tasks/rmic.html
+++ b/docs/manual/Tasks/rmic.html
@@ -56,7 +56,7 @@ attribute. or a nested element.
  <li>sun (the standard compiler of the JDK)</li>
  <li>kaffe (the standard compiler of <a href="http://www.kaffe.org" target="_top">Kaffe</a>)</li>
  <li>weblogic</li>
  <li>forking - the sun compiler forked into a separate process (since Ant 1.7)</li>
  <li>forking - the sun compiler forked into a separate process (since Apache Ant 1.7)</li>
  <li>xnew - the sun compiler forked into a separate process,
      with the -Xnew option (since Ant 1.7).
      This is the most reliable way to use -Xnew</li>
--- a/docs/manual/Tasks/rpm.html
+++ b/docs/manual/Tasks/rpm.html
@@ -83,7 +83,7 @@
    <td valign="top">The executable to use for building the RPM.
      Defaults to <code>rpmbuild</code> if it can be found or
      <code>rpm</code> otherwise.  Set this if you don't have either on
      your PATH or want to use a different executable.  <em>Since Ant
      your PATH or want to use a different executable.  <em>Since Apache Ant
      1.6</em>.</td>
    <td valign="top" align="center">No</td>
  </tr>
--- a/docs/manual/Tasks/scp.html
+++ b/docs/manual/Tasks/scp.html
@@ -27,7 +27,7 @@
 <h2><a name="scp">SCP</a></h2>
 <h3>Description</h3>
 <p><em>since Ant 1.6</em></p>
 <p><em>since Apache Ant 1.6</em></p>
 <p>Copies a file or FileSet to or from a (remote) machine running an SSH daemon.
 FileSet <i>only</i> works for copying files from the local machine to a
--- a/docs/manual/Tasks/script.html
+++ b/docs/manual/Tasks/script.html
@@ -32,7 +32,7 @@
    <a href="https://scripting.dev.java.net">JSR 223</a>  supported language.
  </p>
  <p><b>Note:</b>
    This task depends on external libraries not included in the Ant distribution.
    This task depends on external libraries not included in the Apache Ant distribution.
    See <a href="../install.html#librarydependencies">Library Dependencies</a>
    for more information.
  </p>
--- a/docs/manual/Tasks/scriptdef.html
+++ b/docs/manual/Tasks/scriptdef.html
@@ -26,7 +26,7 @@
 <h2><a name="script">Scriptdef</a></h2>
 <h3>Description</h3>
 <p>Scriptdef can be used to define an Ant task using a scripting language. Ant
 <p>Scriptdef can be used to define an Apache Ant task using a scripting language. Ant
 scripting languages supported by
 <a href="http://jakarta.apache.org/bsf" target="_top">Apache BSF</a> 
 or
--- a/docs/manual/Tasks/sequential.html
+++ b/docs/manual/Tasks/sequential.html
@@ -26,7 +26,7 @@
 <h2>Sequential</h2>
 <h3>Description</h3>
 <p>Sequential is a container task - it can contain other Ant tasks. The nested 
 <p>Sequential is a container task - it can contain other Apache Ant tasks. The nested 
 tasks are simply executed in sequence. Sequential's primary use is to support 
 the sequential execution of a subset of tasks within the 
 <a href="parallel.html">parallel</a> task</p>
--- a/docs/manual/Tasks/serverdeploy.html
+++ b/docs/manual/Tasks/serverdeploy.html
@@ -25,7 +25,7 @@
 <body>
 <h1><a name="serverdeploy">ANT ServerDeploy User Manual</a></h1>
 <h1><a name="serverdeploy">Apache Ant ServerDeploy User Manual</a></h1>
 <p>by</p>
 <!-- Names are in alphabetical order, on last name -->
 <ul>
--- a/docs/manual/Tasks/signjar.html
+++ b/docs/manual/Tasks/signjar.html
@@ -145,7 +145,7 @@ block</td>
    <td valign="top">executable</td>
    <td valign="top">Specify a particular <code>jarsigner</code> executable
      to use in place of the default binary (found in the same JDK as
      Ant is running in).<br/>
      Apache Ant is running in).<br/>
      Must support the same command line options as the Sun JDK
      jarsigner command.
      <em>since Ant 1.8.0</em>.</td>
--- a/docs/manual/Tasks/sos.html
+++ b/docs/manual/Tasks/sos.html
@@ -57,7 +57,7 @@ access to a centralized SourceSafe database via any TCP/IP connection. SOS
 provides Linux ,Solaris &amp; Windows clients. The
 <code> org.apache.tools.ant.taskdefs.optional.sos</code>
 package consists  of a simple framework to support SOS functionality as well
 as some Ant tasks  encapsulating frequently used SOS commands.  Although it
 as some Apache Ant tasks  encapsulating frequently used SOS commands.  Although it
 is possible to use  these commands on the desktop,  they were primarily intended
 to be used by  automated build systems. These tasks have been tested with
 SourceOffSite  version 3.5.1 connecting to VisualSourceSafe 6.0. The tasks
--- a/docs/manual/Tasks/splash.html
+++ b/docs/manual/Tasks/splash.html
@@ -19,7 +19,7 @@
 <head>
 <meta http-equiv="Content-Language" content="en-us">
 <link rel="stylesheet" type="text/css" href="../stylesheets/style.css">
 <title>Ant User Manual</title>
 <title>Apache Ant User Manual</title>
 </head>
 <body>
@@ -59,7 +59,7 @@ whilst waiting for your builds to complete...</p>
      parse the output and dig out current progress. Exactly one group
      pattern must exists, and it represents the progress number (0-100)
      (i.e "Progress: (.*)%")<br/>
      <em>since Ant 1.8.0</em></td>
      <em>since Apache Ant 1.8.0</em></td>
    <td valign="top" align="center">No</td>
    <td valign="top" align="center">progress is increased every action
      and log output line</td>
--- a/docs/manual/Tasks/sql.html
+++ b/docs/manual/Tasks/sql.html
@@ -46,7 +46,7 @@ and <b>abort</b> execution and transaction and fail task.</p>
 <p>
 <b>Proxies</b>. Some JDBC drivers (including the Oracle thin driver), 
    use the JVM's proxy settings to route their JDBC operations to the database.
    Since Ant1.7, Ant running on Java1.5 or later defaults to 
    Since Apache Ant1.7, Ant running on Java1.5 or later defaults to 
    <a href="../proxy.html">using
    the proxy settings of the operating system</a>. 
    Accordingly, the OS proxy settings need to be valid, or Ant's proxy
--- a/docs/manual/Tasks/sshexec.html
+++ b/docs/manual/Tasks/sshexec.html
@@ -27,7 +27,7 @@
 <h2><a name="sshexec">SSHEXEC</a></h2>
 <h3>Description</h3>
 <p><em>since Ant 1.6</em></p>
 <p><em>since Apache Ant 1.6</em></p>
 <p>Runs a command on a remote machine running SSH daemon.
 </p>
--- a/docs/manual/Tasks/sshsession.html
+++ b/docs/manual/Tasks/sshsession.html
@@ -27,7 +27,7 @@
 <h2><a name="sshsession">SSHSESSION</a></h2>
 <h3>Description</h3>
 <p><em>since Ant 1.8.0</em></p>
 <p><em>since Apache Ant 1.8.0</em></p>
 <p>A Task which establishes an SSH connection with a remote machine
 running SSH daemon, optionally establishes any number of local or