Place novelty information for tasks and elements prominently and uniformly

7 years ago · 3ba058c3b5
--- a/manual/Tasks/ant.html
+++ b/manual/Tasks/ant.html
@@ -154,12 +154,13 @@ their <var>id</var>.</p>

 <h4>propertyset</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can specify a set of properties to be copied into the new project
 with <a href="../Types/propertyset.html">propertyset</a>s.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>target</h4>
 <p><em>Since Ant 1.6.3</em>.</p>

 <p>You can specify multiple targets using nested <code>&lt;target&gt;</code> elements instead of
 using the <var>target</var> attribute.  These will be executed as if Ant had been invoked with a
@@ -176,7 +177,6 @@ single target whose dependencies are the targets so specified, in the order spec
    <td>Yes</td>
  </tr>
 </table>
 <p><em>since Ant 1.6.3</em>.</p>

 <h3>Basedir of the new project</h3>

--- a/manual/Tasks/antcall.html
+++ b/manual/Tasks/antcall.html
@@ -129,12 +129,13 @@ their <var>id</var>.</p>

 <h4>propertyset</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can specify a set of properties to be copied into the new project
 with <a href="../Types/propertyset.html">propertyset</a>s.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>target</h4>
 <p><em>Since Ant 1.6.3</em>.</p>

 <p>You can specify multiple targets using nested <code>&lt;target&gt;</code> elements instead of
 using the <var>target</var> attribute.  These will be executed as if Ant had been invoked with a
@@ -151,7 +152,6 @@ single target whose dependencies are the targets so specified, in the order spec
    <td>Yes</td>
  </tr>
 </table>
 <p><em>since Ant 1.6.3</em>.</p>

 <h3>Examples</h3>
 <pre>
--- a/manual/Tasks/antversion.html
+++ b/manual/Tasks/antversion.html
@@ -25,10 +25,10 @@
 <body>

 <h2 id="antversion">Antversion</h2>
 <p><em>Since Ant 1.7.0</em></p>
 <h3>Description</h3>
 <p>Stores the Apache Ant version (when used as task) or checks for a
 specific Ant version (when used as condition). <em>Since Ant
 1.7.0</em></p>
 <p>Stores the Apache Ant version (when used as task) or checks for a specific Ant version (when used
 as condition).</p>

 <table class="attr">
  <tr>
--- a/manual/Tasks/apply.html
+++ b/manual/Tasks/apply.html
@@ -273,7 +273,7 @@ this task and refer to <code>&lt;filelist&gt;</code>s defined elsewhere.</p>
 for this task and refer to <code>&lt;dirset&gt;</code>s defined elsewhere.</p>

 <h4>Any other <a href="../Types/resources.html#collection">Resource Collection</a></h4>
 <p><em>since Ant 1.7</em></p>
 <p><em>Since Ant 1.7</em></p>
 <p>You can use any number of nested resource collections.</p>

 <h4>mapper</h4>
--- a/manual/Tasks/augment.html
+++ b/manual/Tasks/augment.html
@@ -25,13 +25,12 @@
 <body>

 <h2>Augment</h2>

 <p><em>Since Apache Ant 1.8.1</em></p>
 <h3>Description</h3>
 <p>Modify an existing reference by adding nested elements or (re-)assigning properties mapped as XML
 attributes. This is an unusual task that makes use of Ant's internal processing mechanisms to reload
 a previously declared reference by means of the <var>id</var> attribute, then treats the
 declared <code>augment</code> element as though it were the original element. <em>Since Apache Ant
 1.8.1</em></p>
 declared <code>augment</code> element as though it were the original element.</p>

 <h3>Parameters</h3>
 <table class="attr">
--- a/manual/Tasks/bindtargets.html
+++ b/manual/Tasks/bindtargets.html
@@ -25,6 +25,7 @@
 <body>

 <h2 id="ant">Bindtargets</h2>
 <p><em>Since Apache Ant 1.8.2</em></p>
 <h3>Description</h3>

 <p>Make some target the extension of some
@@ -49,8 +50,6 @@ which will be the bridge between the target to bind and the extension point. For
 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><em>Since Apache Ant 1.8.2</em></p>

 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/clearcase.html
+++ b/manual/Tasks/clearcase.html
@@ -725,9 +725,9 @@ named <samp>Application_Baseline_AUTO</samp>.</p>
 <hr/>

 <h2 id="ccmkattr">CCMkattr</h2>
 <p><em>Since Ant 1.6.1</em></p>
 <h3>Description</h3>
 <p>Task to perform a <code>cleartool mkattr</code> command to ClearCase.<br/><em>Since Ant
 1.6.1</em></p>
 <p>Task to perform a <code>cleartool mkattr</code> command to ClearCase.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
@@ -794,9 +794,9 @@ the attribute <samp>BugFix</samp> with a value of <samp>34445</samp> to it.</p>
 <hr/>

 <h2 id="ccmkdir">CCMkdir</h2>
 <p><em>Since Ant 1.6.1</em></p>
 <h3>Description</h3>
 <p>Task to perform a <code>cleartool mkdir</code> command to ClearCase.<br/><em>Since Ant
 1.6.1</em></p>
 <p>Task to perform a <code>cleartool mkdir</code> command to ClearCase.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
@@ -842,9 +842,9 @@ automatically check it out.</p>
 <hr/>

 <h2 id="ccmkelem">CCMkelem</h2>
 <p><em>Since Ant 1.6.1</em></p>
 <h3>Description</h3>
 <p>Task to perform a <code>cleartool mkelem</code> command to ClearCase.<br/><em>Since Ant
 1.6.1</em></p>
 <p>Task to perform a <code>cleartool mkelem</code> command to ClearCase.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/concat.html
+++ b/manual/Tasks/concat.html
@@ -142,17 +142,17 @@

    <h3>Parameters specified as nested elements</h3>
    <h4>Resource Collection</h4>
    <p><em>since Ant 1.7</em>.</p>
    <p><em>Since Ant 1.7</em>.</p>

    <p>Any of the various <a href="../Types/resources.html#collection">Resource Collection</a> types
      can specify the resources to be concatenated.</p>

    <h4>filterchain</h4>
    <p><em>since Ant 1.6</em>.</p>
    <p><em>Since Ant 1.6</em>.</p>
    <p>The concat task supports nested <a href="../Types/filterchain.html">FilterChain</a>s.</p>

    <h4>header, footer</h4>
    <p><em>since Ant 1.6</em>.</p>
    <p><em>Since Ant 1.6</em>.</p>
    <p>Used to prepend or postpend text into the concatenated stream.</p>
    <p>The text may be in-line or be in a file.</p>
    <table class="attr">
--- a/manual/Tasks/conditions.html
+++ b/manual/Tasks/conditions.html
@@ -618,8 +618,9 @@ firewalls.</p>
 <p>Probe for the Maven repository being reachable using the hostname, ten second timeout.</p>

 <h4 id="length">length</h4>
 <p><em>Since Ant 1.6.3</em></p>
 <p>This condition is a facet of the <a href="length.html">Length</a> task. It is used to test the
 length of a string or one or more files.  <em>Since Ant 1.6.3</em></p>
 length of a string or one or more files.</p>

 <pre>&lt;length string=" foo " trim="true" length="3"/&gt;</pre>
 <p>Verify a string is of a certain length.</p>
@@ -628,9 +629,9 @@ length of a string or one or more files.  <em>Since Ant 1.6.3</em></p>
 <p>Verify that file <samp>foo</samp> is not empty.</p>

 <h4 id="isfailure">isfailure</h4>

 <p><em>Since Ant 1.7</em></p>
 <p>Test the return code of an executable (see the <a href="exec.html">Exec</a> task) for
 failure. <em>Since Ant 1.7</em></p>
 failure.</p>

 <table class="attr">
  <tr>
@@ -646,21 +647,23 @@ failure. <em>Since Ant 1.7</em></p>
 </table>

 <h4 id="resourcecount">resourcecount</h4>
 <p><em>Since Ant 1.7</em></p>
 <p>This condition is a facet of the <a href="resourcecount.html">ResourceCount</a> task.  It is used
 to test the size of a <a href="../Types/resources.html#collection">resource
 collection</a>.  <em>Since Ant 1.7</em></p>
 collection</a>.</p>

 <pre>&lt;resourcecount refid=&quot;myresourcecollection&quot; when=&quot;greater&quot; count=&quot;0&quot;/&gt;</pre>
 <p>Verify that a resource collection is not empty.</p>

 <h4 id="resourcesmatch">resourcesmatch</h4>
 <p><em>Since Ant 1.7</em></p>
 <p>Test resources for matching. Nonexistence of one or more resources results in <q>false</q>,
 although if none exists they are considered equal in terms of content.  By default, this test does a
 byte for byte comparison, so test time scales with byte size. <strong>Note</strong>: if the files
 are different sizes, one of them is missing or the filenames match the answer is so obvious the
 detailed test is omitted.  The resources to check are specified as
 nested <a href="../Types/resources.html#collection">resource collections</a>, meaning that more than
 two resources can be checked; in this case all resources must match. <em>Since Ant 1.7</em></p>
 two resources can be checked; in this case all resources must match.</p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
@@ -676,9 +679,10 @@ two resources can be checked; in this case all resources must match. <em>Since A
 </table>

 <h4 id="resourcecontains">resourcecontains</h4>
 <p><em>Since Ant 1.7.1</em></p>
 <p>Tests whether a resource contains a given (sub)string.</p>
 <p>The resources to check are specified via references or&mdash;in the case of file
 resources&mdash;via the resource attribute.  <em>Since Ant 1.7.1</em></p>
 resources&mdash;via the resource attribute.</p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
@@ -707,9 +711,9 @@ resources&mdash;via the resource attribute.  <em>Since Ant 1.7.1</em></p>
 </table>

 <h4 id="hasmethod">hasmethod</h4>

 <p><em>Since Ant 1.7</em></p>
 <p>Tests for a class having a method or field. If the class is not found or fails to load, the build
 fails.  <em>Since Ant 1.7</em></p>
 fails.</p>

 <table class="attr">
  <tr>
@@ -754,9 +758,8 @@ classpath.</p>
 <p>Looks for the method <code>trimToSize()</code> in the <code>java.util.ArrayList</code> class.</p>

 <h4 id="matches">matches</h4>

 <p>Test if the specified string matches the specified regular expression pattern. <em>Since Ant
 1.7</em></p>
 <p><em>Since Ant 1.7</em></p>
 <p>Test if the specified string matches the specified regular expression pattern</p>

 <table class="attr">
  <tr>
@@ -839,8 +842,8 @@ flags.</p>
 are supported, the <var>property</var> attribute is redundant and will be ignored.</p>

 <h4 id="hasfreespace">hasfreespace</h4>

 <p>Tests a partition to see if there is enough space.  <em>Since Ant 1.7.0</em></p>
 <p><em>Since Ant 1.7.0</em></p>
 <p>Tests a partition to see if there is enough space.</p>
 <p>Needed attribute can be specified using standard computing terms:</p>
 <ul>
  <li>K : Kilobytes (1024 bytes)</li>
@@ -871,8 +874,8 @@ are supported, the <var>property</var> attribute is redundant and will be ignore
 <pre>&lt;hasfreespace partition="c:" needed="100M"/&gt;</pre>

 <h4 id="islastmodified">islastmodified</h4>

 <p>Tests the last modified date of a resource.  <em>Since Ant 1.8.0</em></p>
 <p><em>Since Ant 1.8.0</em></p>
 <p>Tests the last modified date of a resource.</p>

 <table class="attr">
  <tr>
@@ -913,8 +916,8 @@ are supported, the <var>property</var> attribute is redundant and will be ignore
 &lt;/islastmodified&gt;</pre>

 <h4 id="resourceexists">resourceexists</h4>

 <p>Tests a resource for existence.  <em>since Ant 1.8.0</em></p>
 <p><em>Since Ant 1.8.0</em></p>
 <p>Tests a resource for existence.</p>

 <p>The actual resource to test is specified as a nested element.</p>

@@ -925,8 +928,8 @@ are supported, the <var>property</var> attribute is redundant and will be ignore
 &lt;/resourceexists&gt;</pre>

 <h4 id="javaversion">javaversion</h4>

 <p>Tests the version of the JVM executing Ant.  <em>Since Ant 1.10.2</em></p>
 <p><em>Since Ant 1.10.2</em></p>
 <p>Tests the version of the JVM executing Ant.</p>

 <table class="attr">
  <tr>
--- a/manual/Tasks/cvsversion.html
+++ b/manual/Tasks/cvsversion.html
@@ -25,9 +25,9 @@
 <body>

 <h2 id="cvs">CvsVersion</h2>
 <p><em>Since Apache Ant 1.6.1</em>.</p>
 <h3>Description</h3>
 <p>This task allows to retrieve a CVS client and server version.  <em>Since Apache Ant
 1.6.1</em>.</p>
 <p>This task allows to retrieve a CVS client and server version.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/defaultexcludes.html
+++ b/manual/Tasks/defaultexcludes.html
@@ -24,9 +24,9 @@

 <body>

 <h2 id="echo">DefaultExcludes</h2>
 <h2 id="defaultexcludes">DefaultExcludes</h2>

 <p><em>since Apache 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 build, and prints out the
--- a/manual/Tasks/dependset.html
+++ b/manual/Tasks/dependset.html
@@ -88,8 +88,10 @@ filelists may be specified.</p>

 <h4>targets</h4>

 <p><em>Since Ant 1.7</em></p>

 <p>The <code>&lt;targets&gt;</code> element is a <a href="../using.html#path">Path</a> and thus can
 include any filesystem-based resource. <em>Since Ant 1.7</em></p>
 include any filesystem-based resource.</p>

 <h4>targetfileset</h4>

--- a/manual/Tasks/diagnostics.html
+++ b/manual/Tasks/diagnostics.html
@@ -25,9 +25,10 @@
 <body>

 <h2 id="diagnostics">Diagnostics</h2>
 <p><em>Since Ant 1.7.0</em></p>
 <h3>Description</h3>
 <p>Runs Apache Ant's <code>-diagnostics</code> code inside Ant itself. This is good for debugging
 Ant's configuration under an IDE. <em>Since Ant 1.7.0</em></p>
 Ant's configuration under an IDE.</p>

 <h3>Examples</h3>

--- a/manual/Tasks/echoproperties.html
+++ b/manual/Tasks/echoproperties.html
@@ -78,13 +78,13 @@ files.</p>

 <h4>propertyset</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can specify subsets of properties to be echoed
 with <a href="../Types/propertyset.html">propertyset</a>s. Using <code>propertyset</code>s gives
 more control on which properties will be picked up. The attributes <var>prefix</var>
 and <var>regex</var> are just shortcuts that use <code>propertyset</code>s internally.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h3>Examples</h3>
 <pre>&lt;echoproperties/&gt;</pre>
 <p>Report the current properties to the log.</p>
--- a/manual/Tasks/echoxml.html
+++ b/manual/Tasks/echoxml.html
@@ -25,8 +25,9 @@
 <body>

 <h2>EchoXML</h2>
 <p><em>Since Apache Ant 1.7</em></p>
 <h3>Description</h3>
 <p>Echo nested XML to the console or a file. <em>Since Apache Ant 1.7</em></p>
 <p>Echo nested XML to the console or a file.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/import.html
+++ b/manual/Tasks/import.html
@@ -173,8 +173,8 @@
 <h3>Parameters specified as nested elements</h3>

 <h4>any <a href="../Types/resources.html">resource</a> or resource collection</h4>

 <p>The specified resources will be imported.  <em>Since Ant 1.8.0</em></p>
 <p><em>Since Ant 1.8.0</em></p>
 <p>The specified resources will be imported.</p>

 <h3>Examples</h3>
 <pre>&lt;import file=&quot;../common-targets.xml&quot;/&gt;</pre>
--- a/manual/Tasks/include.html
+++ b/manual/Tasks/include.html
@@ -22,11 +22,10 @@
 </head>
 <body>
  <h2 id="include">Include</h2>
  <p><em>Since Apache Ant 1.8.0</em></p>
  <h3>Description</h3>
  <p>Include another build file into the current project.</p>

  <p><em>since Apache Ant 1.8.0</em></p>

  <p><strong>Note</strong> 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 default, this task may or may not work.</p>
@@ -37,8 +36,10 @@
    in the Ant FAQ</a> insofar as the target names get prefixed by the included
    project's <var>name</var> or <var>as</var> attribute and do not appear as if the file was
    contained in the including file.</p>

  <p>The <code>include</code> task may only be used as a top-level task. This means that
    it may not be used in a target.</p>

  <p>There are two further functional aspects that pertain to this task and that are not possible
    with entity includes:</p>
  <ul>
--- a/manual/Tasks/jar.html
+++ b/manual/Tasks/jar.html
@@ -329,7 +329,7 @@ as appropriate.</p>

 <h4 id="indexjars">indexjars</h4>

 <p><em>since Ant 1.6.2</em></p>
 <p><em>Since Ant 1.6.2</em></p>

 <p>The nested <code>indexjars</code> element specifies a <a href="../using.html#path">path-like
 structure</a>.  Its content is completely ignored unless you set the <var>index</var> attribute of
@@ -352,7 +352,7 @@ to <q>true</q>.</p>

 <h4 id="service">service</h4>

 <p><em>since Ant 1.7.0</em></p>
 <p><em>Since Ant 1.7.0</em></p>

 <p>The nested <code>service</code> element specifies a service.  Services are described in
 the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#Service_Provider">service
--- a/manual/Tasks/java.html
+++ b/manual/Tasks/java.html
@@ -225,23 +225,23 @@ for <a href="exec.html#env">environment variables</a>.</p>

 <h4>syspropertyset</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can specify a set of properties to be used as system properties
 with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>classpath</h4>
 <p><code>Java</code>'s <var>classpath</var> attribute is a <a href="../using.html#path">path-like
 structure</a> and can also be set via a nested <code>classpath</code> element.</p>

 <h4>bootclasspath</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>The location of bootstrap class files can be specified using
 this <a href="../using.html#path">path-like structure</a>&mdash;will be ignored if <var>fork</var>
 is not <q>true</q> or the target JVM doesn't support it (i.e. Java 1.1).</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>env</h4>
 <p>It is possible to specify environment variables to pass to the forked JVM via
 nested <code>env</code> elements. See the description in the section
@@ -249,6 +249,9 @@ about <a href="exec.html#env">exec</a></p>
 <p>Settings will be ignored if <var>fork</var> is <q>false</q>.</p>

 <h4>permissions</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>Security permissions can be revoked and granted during the execution of the class via a
 nested <code>permissions</code> element. For more information please
 see <a href="../Types/permissions.html">permissions</a>.</p>
@@ -261,17 +264,15 @@ indicated by <var>failonerror</var>. All permissions not granted per default wil
 whatever security manager was already in place. <code>exitVM</code> will be disallowed.</p>
 <p>Settings will be ignored if <var>fork</var> is <q>true</q>.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>assertions</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can control enablement of Java 1.4 assertions with
 an <a href="../Types/assertions.html"><code>&lt;assertions&gt;</code></a> subelement.</p>

 <p>Assertion statements are currently ignored in non-forked mode.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4 id="redirector">redirector</h4>
 <em>Since Ant 1.6.2</em>
 <p>A nested <a href="../Types/redirector.html">I/O Redirector</a> can be specified.  In general, the
--- a/manual/Tasks/javac.html
+++ b/manual/Tasks/javac.html
@@ -474,15 +474,14 @@ can be used to enable arguments only if a given compiler implementation will be
  </tr>
 </table>

 <h4>compilerclasspath (<em>since Ant 1.8.0</em>)</h4>

 <h4>compilerclasspath</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>A <a href="../using.html#path">path-like structure</a> holding the classpath to use when loading
 the compiler implementation if a custom class has been specified.  Doesn't have any effect when
 using one of the built-in compilers.</p>

 <h4>Any nested element of a type that implements <code>CompilerAdapter</code> (<em>since Ant
 1.8.0</em>)</h4>

 <h4>Any nested element of a type that implements <code>CompilerAdapter</code></h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>If a defined type implements the <code>CompilerAdapter</code> interface a nested element of that
 type can be used as an alternative to the <var>compiler</var> attribute.</p>

--- a/manual/Tasks/javadoc.html
+++ b/manual/Tasks/javadoc.html
@@ -789,9 +789,9 @@ nested <code>sourcepath</code>, <code>classpath</code> and <code>bootclasspath</
 respectively.</p>

 <h4>arg</h4>

 <p><em>Since Ant 1.6</em></p>
 <p>Use nested <code>&lt;arg&gt;</code> to specify additional arguments.
 See <a href="../using.html#arg">Command line arguments</a>. <em>Since Ant 1.6</em></p>
 See <a href="../using.html#arg">Command line arguments</a>.</p>

 <h3>Example</h3>
 <pre>
--- a/manual/Tasks/javah.html
+++ b/manual/Tasks/javah.html
@@ -176,14 +176,14 @@ can be used to enable arguments only if a given compiler implementation will be
  </tr>
 </table>

 <h4>implementationclasspath (<em>since Ant 1.8.0</em>)</h4>

 <h4>implementationclasspath</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>A <a href="../using.html#path">path-like structure</a> holding the classpath to use when loading
 the compiler implementation if a custom class has been specified.  Doesn't have any effect when
 using one of the built-in compilers.</p>

 <h4>Any nested element of a type that implements JavahAdapter (<em>since Ant 1.8.0</em>)</h4>

 <h4>Any nested element of a type that implements JavahAdapter</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>If a defined type implements the <code>JavahAdapter</code> interface a nested element of that
 type can be used as an alternative to the <var>implementation</var> attribute.</p>

--- a/manual/Tasks/junit.html
+++ b/manual/Tasks/junit.html
@@ -154,8 +154,7 @@ for details.</p>
  </tr>
  <tr>
    <td>outputtoformatters</td>
    <td><em>Since Ant 1.7.0</em>.<br/>Send any output generated by tests to the test
      formatters.</td>
    <td>Send any output generated by tests to the test formatters.  <em>Since Ant 1.7.0</em>.</td>
    <td>No; default is <q>true</q></td>
  </tr>
  <tr>
@@ -268,11 +267,11 @@ test.</p>

 <h4>syspropertyset</h4>

 <p><em>Since Ant 1.6</em></p>

 <p>You can specify a set of properties to be used as system properties
 with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>env</h4>

 <p>It is possible to specify environment variables to pass to the forked JVM via
@@ -283,46 +282,47 @@ element's attributes, see the description in the <a href="../Tasks/exec.html#env

 <h4>bootclasspath</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>The location of bootstrap class files can be specified using
 this <a href="../using.html#path">PATH like structure</a>&mdash;will be ignored if <var>fork</var>
 is <q>false</q> or the target JVM doesn't support it (i.e. Java 1.1).</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>permissions</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>Security permissions can be revoked and granted during the execution of the class via a
 nested <code>permissions</code> element. For more information please
 see <a href="../Types/permissions.html">permissions</a></p>

 <p>Settings will be ignored if <var>fork</var>=<q>true</q>.</p>

 <p><em>since Ant 1.6</em>.</p>

 <h4>assertions</h4>

 <p><em>Since Ant 1.6</em>.</p>

 <p>You can control enablement of Java 1.4 assertions with
 an <a href="../Types/assertions.html"><code>&lt;assertions&gt;</code></a> subelement.</p>

 <p>Assertion statements are currently ignored in non-forked mode.</p>

 <p><em>Since Ant 1.6</em>.</p>

 <h4>modulepath</h4>

 <p><em>Since Ant 1.9.8</em></p>

 <p>The location of modules can be specified using this <a href="../using.html#path">PATH like
 structure</a>.<br/>The <code>modulepath</code> requires <var>fork</var> to be set to <q>true</q>.

 <p><em>since Ant 1.9.8</em></p>

 <h4>upgrademodulepath</h4>

 <p><em>Since Ant 1.9.8</em></p>

 <p>The location of modules that replace upgradeable modules in the runtime image can be specified
 using this <a href="../using.html#path">PATH like
 structure</a>.<br/>The <code>upgrademodulepath</code> requires <var>fork</var> to be set
 to <q>true</q>.</p>

 <p><em>since Ant 1.9.8</em></p>

 <h4>formatter</h4>

 <p>The results of the tests can be printed in different formats. Output will always be sent to a
--- a/manual/Tasks/length.html
+++ b/manual/Tasks/length.html
@@ -25,10 +25,11 @@
 <body>

 <h2>Length</h2>
 <p><em>Since Apache Ant 1.6.3</em></p>
 <h3>Description</h3>
 <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 <code>condition</code>. <em>Since Apache Ant 1.6.3</em></p>
 a <code>condition</code>.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/loadproperties.html
+++ b/manual/Tasks/loadproperties.html
@@ -85,7 +85,9 @@ the <a href="property.html"><code>&lt;property&gt;</code></a> task.</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><em>Since Ant 1.7</em></p>

 <p>The specified resource will be used as <var>srcFile</var> or <var>resource</var>.</p>

 <h4><a href="../Types/filterchain.html">FilterChain</a></h4>

--- a/manual/Tasks/local.html
+++ b/manual/Tasks/local.html
@@ -25,6 +25,7 @@
 <body>

 <h2>Local</h2>
 <p><em>Since Ant 1.8</em></p>
 <h3>Description</h3>
 <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>
@@ -33,10 +34,10 @@ and <a href="sequential.html">Sequential</a> task containers
 properties of the same name at higher scopes, including the global scope. Note that using
 the <code>Local</code> task at the global level effectively makes the property local to the
 "anonymous target" in which top-level operations are carried out; it will not be defined for other
 targets in the buildfile. <em>Since Ant 1.8</em></p>
 targets in the buildfile.</p>

 <p>A property is made local if the <code>&lt;local&gt;</code> task
  precedes its definition.  See the examples section.</p>
 <p>A property is made local if the <code>&lt;local&gt;</code> task precedes its definition.  See the
 examples section.</p>

 <h3>Parameters</h3>
 <table class="attr">
--- a/manual/Tasks/macrodef.html
+++ b/manual/Tasks/macrodef.html
@@ -25,6 +25,7 @@
  <body>

    <h2 id="macrodef">MacroDef</h2>
    <p><em>Since Apache Ant 1.6</em></p>
    <h3>Description</h3>
    <p>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
@@ -33,7 +34,6 @@
    <h3>Note</h3>
    <p>You can also use <em>prior defined</em> attributes for <var>default</var> values in other
      attributes. See the examples.</p>
    <p><em>since Apache Ant 1.6</em></p>
    <h3>Parameters</h3>
    <table class="attr">
      <tr>
--- a/manual/Tasks/manifestclasspath.html
+++ b/manual/Tasks/manifestclasspath.html
@@ -25,6 +25,7 @@
 <body>

 <h2 id="manifestclasspath">Manifestclasspath</h2>
 <p><em>Since Apache Ant 1.7</em></p>

 <h3>Description</h3>
 <p>Converts a <a href="../using.html#path">Path</a> into a property whose value is appropriate for
@@ -47,8 +48,6 @@ element, where the defined property is re-referenced.</p>
 attribute to the elements of the nested <code>classpath</code> must be the same as you expect them
 to be when deploying the jar.</p>

 <p><em>since Apache Ant 1.7</em></p>

 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/native2ascii.html
+++ b/manual/Tasks/native2ascii.html
@@ -161,14 +161,14 @@ can be used to enable arguments only if a given converter implementation will be
  </tr>
 </table>

 <h4>implementationclasspath (<em>since Apache Ant 1.8.0</em>)</h4>

 <h4>implementationclasspath</h4>
 <p><em>Since Apache Ant 1.8.0</em></p>
 <p>A <a href="../using.html#path">path-like structure</a> holding the classpath to use when loading
 the converter implementation if a custom class has been specified.  Doesn't have any effect when
 using one of the built-in converters.</p>

 <h4>Any nested element of a type that implements Native2AsciiAdapter (<em>since Ant 1.8.0</em>)</h4>

 <h4>Any nested element of a type that implements Native2AsciiAdapter</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>If a defined type implements the <code>Native2AsciiAdapter</code> interface a nested element of
 that type can be used as an alternative to the <var>implementation</var> attribute.</p>

@@ -178,8 +178,8 @@ that type can be used as an alternative to the <var>implementation</var> attribu
 &lt;native2ascii encoding=&quot;EUCJIS&quot; src=&quot;srcdir&quot; dest=&quot;srcdir&quot;
              includes=&quot;**/*.eucjis&quot; ext=&quot;.java&quot;/&gt;</pre>

    <p>Converts all files in the directory <samp>srcdir</samp> ending in <samp>.eucjis</samp> from
      the EUCJIS encoding to ASCII and renames them to end in <samp>.java</samp>.</p>
 <p>Converts all files in the directory <samp>srcdir</samp> ending in <samp>.eucjis</samp> from the
 EUCJIS encoding to ASCII and renames them to end in <samp>.java</samp>.</p>

 <pre>
 &lt;native2ascii encoding=&quot;EUCJIS&quot; src=&quot;native/japanese&quot; dest=&quot;src&quot;
--- a/manual/Tasks/pack.html
+++ b/manual/Tasks/pack.html
@@ -56,8 +56,8 @@ See <a href="../install.html#librarydependencies">Library Dependencies</a> for m
  </tr>
 </table>
 <h4>any <a href="../Types/resources.html">resource</a> or single element resource collection</h4>

 <p>The specified resource will be used as <var>src</var>. <em>Since Apache Ant 1.7</em></p>
 <p><em>Since Apache Ant 1.7</em></p>
 <p>The specified resource will be used as <var>src</var>.</p>

 <h3>Examples</h3>
 <pre>&lt;gzip src=&quot;test.tar&quot; destfile=&quot;test.tar.gz&quot;/&gt;</pre>
--- a/manual/Tasks/presetdef.html
+++ b/manual/Tasks/presetdef.html
@@ -25,10 +25,10 @@
  <body>

    <h2 id="presetdef">PreSetDef</h2>
    <p><em>Since Apache Ant 1.6</em></p>
    <h3>Description</h3>
    <p>The preset definition generates a new definition based on a current definition with some
      attributes or elements preset.</p>
    <p><em>since Apache Ant 1.6</em></p>
    <p>The resolution of properties in any of the attributes or nested text takes place with the
      definition is used and <em>not</em> when the preset definition is defined.</p>
    <h3>Parameters</h3>
--- a/manual/Tasks/projecthelper.html
+++ b/manual/Tasks/projecthelper.html
@@ -25,6 +25,7 @@
 <body>

 <h2>ProjectHelper</h2>
 <p><em>Since Ant 1.8.2</em></p>
 <h3>Description</h3>
 <p>This task is provided for the purpose of allowing the user to install a different ProjectHelper
 at runtime.</p>
@@ -32,7 +33,6 @@ at runtime.</p>
 (<code>ProjectHelper2</code>)</p>
 <p>See the description of Apache Ant's <a href="../projecthelper.html">Project Helper</a> for more
 information.</p>
 <p><em>Since Ant 1.8.2</em></p>

 <h3>Parameters specified as nested elements</h3>

--- a/manual/Tasks/propertyhelper.html
+++ b/manual/Tasks/propertyhelper.html
@@ -25,14 +25,14 @@
 <body>

 <h2>PropertyHelper</h2>
 <p><em>Since Ant 1.8.0</em></p>
 <h3>Description</h3>
 <p>This task is provided for the purpose of allowing the user to <strong>(a)</strong> install a
 different <code>PropertyHelper</code> at runtime, or <strong>(b)</strong> (hopefully more often)
 install one or more <code>PropertyHelper</code> Delegates into the <code>PropertyHelper</code>
 active on the current <code>Project</code>. 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.
 <em>Since Ant 1.8.0</em></p>
 Ant's <a href="../properties.html#propertyHelper">Property Helper</a> for more information.</p>

 <h3>Parameters specified as nested elements</h3>

--- a/manual/Tasks/resourcecount.html
+++ b/manual/Tasks/resourcecount.html
@@ -25,11 +25,11 @@
 <body>

 <h2>ResourceCount</h2>

 <p><em>Since Apache Ant 1.7</em></p>
 <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. <em>Since Apache Ant 1.7</em></p>
 condition.</p>
 <h3>Parameters</h3>
 <table class="attr">
  <tr>
--- a/manual/Tasks/retry.html
+++ b/manual/Tasks/retry.html
@@ -23,10 +23,11 @@
 </head>
 <body>
 <h2>Retry</h2>
 <p><em>Since Apache Ant 1.7.1</em></p>
 <h3>Description</h3>
 <p><code>Retry</code> is a container which executes a single nested task until either: there is no
 failure; or: its <var>retrycount</var> has been exceeded. If this happens a BuildException is
 thrown. <em>Since Apache Ant 1.7.1</em></p>
 thrown.</p>

 <h3>Parameters</h3>
 <table class="attr">
--- a/manual/Tasks/rmic.html
+++ b/manual/Tasks/rmic.html
@@ -276,14 +276,14 @@ can be used to enable arguments only if a given compiler implementation will be
  </tr>
 </table>

 <h4>compilerclasspath (<em>since Ant 1.8.0</em>)</h4>

 <h4>compilerclasspath</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>A <a href="../using.html#path">path-like structure</a> holding the classpath to use when loading
 the compiler implementation if a custom class has been specified.  Doesn't have any effect when
 using one of the built-in compilers.</p>

 <h4>Any nested element of a type that implements RmicAdapter (<em>since Ant 1.8.0</em>)</h4>

 <h4>Any nested element of a type that implements RmicAdapter</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>If a defined type implements the <code>RmicAdapter</code> interface a nested element of that type
 can be used as an alternative to the <var>compiler</var> attribute.</p>

--- a/manual/Tasks/scp.html
+++ b/manual/Tasks/scp.html
@@ -25,10 +25,9 @@
 <body>

 <h2 id="scp">SCP</h2>
 <p><em>Since Apache Ant 1.6</em></p>
 <h3>Description</h3>

 <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 <em>only</em> works for copying files from the local machine to a remote machine.</p>

--- a/manual/Tasks/sshexec.html
+++ b/manual/Tasks/sshexec.html
@@ -25,10 +25,9 @@
 <body>

 <h2 id="sshexec">SSHEXEC</h2>
 <p><em>Since Apache Ant 1.6</em></p>
 <h3>Description</h3>

 <p><em>since Apache Ant 1.6</em></p>

 <p>Runs a command on a remote machine running SSH daemon.</p>

 <p><strong>Note</strong>: This task depends on external libraries not included in the Ant
--- a/manual/Tasks/sshsession.html
+++ b/manual/Tasks/sshsession.html
@@ -25,10 +25,9 @@
 <body>

 <h2 id="sshsession">SSHSESSION</h2>
 <p><em>Since Apache Ant 1.8.0</em></p>
 <h3>Description</h3>

 <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 remote tunnels over that connection, then executes any nested
 tasks before taking down the connection.</p>
--- a/manual/Tasks/style.html
+++ b/manual/Tasks/style.html
@@ -242,7 +242,7 @@ path-like structure).</p>

 <h4>any <a href="../Types/resources.html#collection">resource collection</a></h4>

 <p><em>since Ant 1.7</em></p>
 <p><em>Since Ant 1.7</em></p>

 <p>Use resource collections to specify resources that the stylesheet should be applied to.  Use a
 nested mapper and the task's <q>destdir</q> attribute to specify the output files.</p>
@@ -341,6 +341,7 @@ the <a href="https://www.w3.org/TR/xslt#output"> XSLT specifications</a>.
 </table>

 <h4 id="factory">factory (<var>trax</var> processors only)</h4>
 <p><em>Since Ant 1.9.8</em></p>
 <p>Used to specify factory settings.</p>

 <h5>Parameters</h5>
@@ -425,7 +426,6 @@ documentation of your processor.  For example, in Xalan 2.x:</p>

 <p>Sets the classloader to use when loading extension functions to a classloader using
 the <code>path</code> with the id <code>extension-path</code>.</p>
 <p><em>since Ant 1.9.8</em></p>

 <h6>feature</h6>
 <p>Used to specify settings of the processor factory.  The feature names are mostly processor
@@ -456,7 +456,7 @@ is <var>http://javax.xml.XMLConstants/feature/secure-processing</var>.

 <h4>mapper</h4>

 <p><em>since Ant 1.6.2</em></p>
 <p><em>Since Ant 1.6.2</em></p>

 <p>You can define filename transformations by using a
 nested <a href="../Types/mapper.html">mapper</a> element. The default mapper used
@@ -473,20 +473,20 @@ should be specified as a nested resource or single-element collection.  Alternat
 the <var>refid</var> to specify the resource or collection as a reference.</p>

 <h4>sysproperty</h4>

 <p><em>Since Ant 1.8.0</em>.</p>
 <p>Use nested <code>&lt;sysproperty&gt;</code> elements to specify system properties required by the
 factory or transformation.  These properties will be made available to JVM during the execution of
 the class. The attributes for this element are the same as for <a href="exec.html#env">environment
 variables</a>.</p>

 <p><em>since Ant 1.8.0</em>.</p>

 <h4>syspropertyset</h4>

 <p><em>Since Ant 1.8.0</em>.</p>

 <p>You can specify a set of properties to be used as system properties
 with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>

 <p><em>since Ant 1.8.0</em>.</p>

 <h3>Examples</h3>
 <pre>
 &lt;xslt basedir=&quot;doc&quot; destdir=&quot;build/doc&quot;
--- a/manual/Tasks/subant.html
+++ b/manual/Tasks/subant.html
@@ -24,11 +24,11 @@

 <body>
 <h2>Subant Task</h2>
 <p><em>Since Apache Ant 1.6</em></p>
 <h3 id="description">Description</h3>
 <p>Calls a given target for all defined sub-builds.  This is an extension of Ant for bulk project
 execution.  <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>
 <p><em>Since Apache Ant 1.6</em></p>

 <p><code>subant</code> uses <code>ant</code> internally so many things said
 in <a href="ant.html"><code>ant</code>'s manual page</a> apply here as well.</p>
@@ -140,6 +140,7 @@ different from the way <code>&lt;property&gt;</code> tasks in build files behave
 <p>Creates a nested <code>&lt;buildpathelement&gt;</code>, and add it to the implicit build
 path.</p>
 <h4><strong>target</strong> (org.apache.tools.ant.taskdefs.Ant.TargetElement)</h4>
 <p><em>Since Ant 1.7</em>.</p>
 <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>
@@ -155,7 +156,6 @@ whose dependencies are the targets so specified, in the order specified.</p>
    <td>Yes</td>
  </tr>
 </table>
 <p><em>since Ant 1.7</em>.</p>
 <h3 id="examples">Examples</h3>
 <pre>
 &lt;project name="subant" default="subant1"&gt;
--- a/manual/Tasks/truncate.html
+++ b/manual/Tasks/truncate.html
@@ -25,12 +25,12 @@
 <body>

 <h2 id="touch">Truncate</h2>
 <p><em>Since Apache Ant 1.7.1</em></p>
 <h3>Description</h3>

 <p>Set the length of one or more files, as the intermittently available <code>truncate</code> Unix
 utility/function. In addition to working with a single file, this Task can also work
 on <a href="../Types/resources.html">resources</a> and resource collections. <em>Since Apache Ant
 1.7.1</em>.</p>
 on <a href="../Types/resources.html">resources</a> and resource collections.</p>

 <h3>Parameters</h3>
 <table class="attr">
--- a/manual/Tasks/uptodate.html
+++ b/manual/Tasks/uptodate.html
@@ -85,9 +85,10 @@ to directories as well, use a nested <code>srcresources</code> element and a <co
 (for example).</p>

 <h4 id="srcresources">srcresources</h4>
 <p><em>Since Apache Ant 1.7</em></p>
 <p>The nested <code>&lt;srcresources&gt;</code> element is
 a <a href="../Types/resources.html#union">union</a> and allows you to specify a collection of
 resources to check against the target file(s). <em>Since Apache Ant 1.7</em></p>
 resources to check against the target file(s).</p>

 <h4 id="mapper">mapper</h4>
 <p>The nested <code>&lt;mapper&gt;</code> element allows you to specify a set of target files to
--- a/manual/Types/filterchain.html
+++ b/manual/Types/filterchain.html
@@ -441,9 +441,9 @@ and of the choice of regular expression implementation.</p>

 <h3 id="suffixlines">SuffixLines</h3>

 <p>Attaches a suffix to every line.</p>
 <p><em>Since Ant 1.8.0</em></p>

 <p><em>since Ant 1.8.0</em></p>
 <p>Attaches a suffix to every line.</p>

 <table class="attr">
  <tr>
@@ -887,8 +887,10 @@ extracted)</p>

 <h3 id="deletecharacters">DeleteCharacters</h3>

 <p><em>Since Ant 1.6</em></p>

 <p>This filter deletes specified characters.</p>
 <p><em>since Ant 1.6</em></p>

 <p>This filter is only available in the convenience form.</p>

 <table class="attr">
@@ -912,8 +914,8 @@ extracted)</p>
 <pre>&lt;deletecharacters chars="\t\r"/&gt;</pre>

 <h3 id="concatfilter">ConcatFilter</h3>
 <p><em>Since Ant 1.6</em></p>
 <p>This filter prepends or appends the content file to the filtered files.</p>
 <p><em>since Ant 1.6</em></p>
 <table class="attr">
  <tr>
    <th>Parameter Name</th>
@@ -952,7 +954,7 @@ extracted)</p>
 &lt;/filterchain&gt;</pre>

 <h3 id="sortfilter">SortFilter</h3>
 <p><em>since Ant 1.8.0</em></p>
 <p><em>Since Ant 1.8.0</em></p>

 <p>The sort filter reads all lines and sorts them.  The sort order can be reversed and it is
 possible to specify a custom implementation of the <code>java.util.Comparator</code> interface
@@ -1414,11 +1416,12 @@ sort filter.</p>

 <h4 id="native2asciifilter">Native2AsciiFilter</h4>

 <p><em>Since Ant 1.9.8</em></p>

 <p>Uses the "builtin" implementation of
 the <a href="../Tasks/native2ascii.html">native2ascii</a> task.</p>

 <p>Replaces non-ascii characters by their Unicode-escapes or vice-versa.  <em>Since Ant
 1.9.8</em></p>
 <p>Replaces non-ASCII characters by their Unicode-escapes or vice-versa.</p>

 <p>This filter may be used directly within a <code>filterchain</code>.</p>

--- a/manual/Types/mapper.html
+++ b/manual/Types/mapper.html
@@ -541,7 +541,8 @@ with <code>&lt;uptodate&gt;</code> and <code>&lt;junit&gt;</code> output.</p>
    <!--           Unpackage Mapper             -->
    <!--                                        -->

 <h4 id="unpackage-mapper">unpackage (<em>since Ant 1.6.0</em>)</h4>
 <h4 id="unpackage-mapper">unpackage</h4>
 <p><em>Since Ant 1.6.0</em></p>
 <p>This mapper is the inverse of the <a href="#package-mapper">package</a> mapper.  It replaces
 the dots in a package name with directory separators. This is useful for matching XML formatter
 results against their JUnit test test cases. The mapper shares the sample syntax as
@@ -566,7 +567,8 @@ the <a href="#glob-mapper">glob mapper</a>.</p>
    <!--           Composite Mapper             -->
    <!--                                        -->

 <h4 id="composite-mapper">composite (<em>since Ant 1.7.0</em>)</h4>
 <h4 id="composite-mapper">composite</h4>
 <p><em>Since Ant 1.7.0</em></p>
 <p>This mapper implementation can contain multiple nested mappers.  File mapping is performed by
 passing the source filename to each nested <code>&lt;mapper&gt;</code> in turn, returning all
 results.  The <var>to</var> and <var>from</var> attributes are ignored.</p>
@@ -598,7 +600,8 @@ attribute.</p>
    <!--            Chained Mapper              -->
    <!--                                        -->

 <h4 id="chained-mapper">chained (<em>since Ant 1.7.0</em>)</h4>
 <h4 id="chained-mapper">chained</h4>
 <p><em>Since Ant 1.7.0</em></p>
 <p>This mapper implementation can contain multiple nested mappers.  File mapping is performed by
 passing the source filename to the first nested mapper, its results to the second, and so on.
 The target filenames generated by the last nested mapper comprise the ultimate results of the
@@ -640,7 +643,8 @@ attribute.</p>
    <!--             Filter Mapper              -->
    <!--                                        -->

 <h4 id="filter-mapper">filtermapper (<em>since Ant 1.6.3</em>)</h4>
 <h4 id="filter-mapper">filtermapper</h4>
 <p><em>Since Ant 1.6.3</em></p>
 <p>This mapper implementation applies a <a href="filterchain.html">filterchain</a> to the source
 file name.</p>
 <h5>Examples</h5>
@@ -685,7 +689,8 @@ file name.</p>
    <!--             Script Mapper              -->
    <!--                                        -->

 <h4 id="script-mapper">scriptmapper (<em>since Ant 1.7</em>)</h4>
 <h4 id="script-mapper">scriptmapper</h4>
 <p><em>Since Ant 1.7</em></p>
 <p>This mapper executes a script written in <a href="https://jakarta.apache.org/bsf"
 target="_top">Apache BSF</a>
 or <a href="https://jcp.org/aboutJava/communityprocess/maintenance/jsr223/223ChangeLog.html">JSR
@@ -793,7 +798,8 @@ every source file, with the list of mapped names reset after every invocation.</

 <p>The scriptmapper has no corresponding <code>&lt;mapper <var>type</var>&gt;</code> attribute.</p>

 <h4 id="firstmatch-mapper">firstmatchmapper (<em>since Ant 1.8.0</em>)</h4>
 <h4 id="firstmatch-mapper">firstmatchmapper</h4>
 <p><em>Since Ant 1.8.0</em></p>
 <p>This mapper supports an arbitrary number of nested mappers and returns the results of the
 first mapper that matches.  This is different from <a href="#composite-mapper">composite
 mapper</a> which collects the results of all matching children.</p>
@@ -822,8 +828,8 @@ mapper</a> which collects the results of all matching children.</p>
 <p>The firstmatchmapper has no corresponding <code>&lt;mapper <var>type</var>&gt;</code>
 attribute.</p>

 <h4 id="cutdirs-mapper">cutdirsmapper (<em>since Ant 1.8.2</em>)</h4>

 <h4 id="cutdirs-mapper">cutdirsmapper</h4>
 <p><em>Since Ant 1.8.2</em></p>
 <p>This mapper strips a configured number of leading directories from the source file name.</p>

 <h5>Examples</h5>
--- a/manual/Types/patternset.html
+++ b/manual/Types/patternset.html
@@ -127,8 +127,8 @@ attributes you can use to test the existence of a property.</p>
 <p>Patternsets may be nested within one another, adding the nested patterns to the parent
 patternset.</p>
 <h4><code>invert</code></h4>
 <p>A nested patternset can be inverted using the <code>&lt;invert&gt;</code> element. <em>Since
 Apache Ant 1.7.1</em></p>
 <p><em>Since Apache Ant 1.7.1</em></p>
 <p>A nested patternset can be inverted using the <code>&lt;invert&gt;</code> element.</p>
 <h3>Examples</h3>
 <pre>
 &lt;patternset id=&quot;non.test.sources&quot;&gt;
--- a/manual/Types/redirector.html
+++ b/manual/Types/redirector.html
@@ -25,14 +25,14 @@
 <body>

 <h2 id="redirector">I/O redirection</h2>
 <p><em>Since Apache Ant 1.6.2</em></p>
 <p>For many tasks, input and output can be defined in a fairly straightforward fashion.
 The <a href="../Tasks/exec.html">exec</a> 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 <em>output</em> or
 as <em>error output</em>.  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 Apache Ant
 1.6.2</em></p>
 specify source (input) and destination (output/error) files.</p>
 <p>The <code>&lt;redirector&gt;</code> element accepts the following attributes:</p>
 <table class="attr">
  <tr>
--- a/manual/Types/resources.html
+++ b/manual/Types/resources.html
@@ -938,9 +938,10 @@ first few oldest, largest, etc. resources from a larger collection.</p>
 <p>A single resource collection is required.</p>

 <h4 id="last">last</h4>
 <p><em>Since Ant 1.7.1</em></p>
 <p>Includes the last <var>count</var> resources from a nested resource collection.  This can be
 used in conjunction with the <a href="#sort">sort</a> collection, for example, to select the
 last few oldest, largest, etc. resources from a larger collection. <em>Since Ant 1.7.1</em></p>
 last few oldest, largest, etc. resources from a larger collection.</p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
@@ -962,10 +963,11 @@ last few oldest, largest, etc. resources from a larger collection. <em>Since Ant
 <p>A single resource collection is required.</p>

 <h4 id="allbutfirst">allbutfirst</h4>
 <p><em>Since Ant 1.9.5</em></p>
 <p>Includes all elements except for the first <var>count</var> resources from a nested resource
 collection.  This can be used in conjunction with the <a href="#sort">sort</a> collection, for
 example, to select all but the first few oldest, largest, etc. resources from a larger
 collection. <em>Since Ant 1.9.5</em></p>
 collection.</p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
@@ -987,10 +989,11 @@ collection. <em>Since Ant 1.9.5</em></p>
 <p>A single resource collection is required.</p>

 <h4 id="allbutlast">allbutlast</h4>
 <p><em>Since Ant 1.9.5</em></p>
 <p>Includes all elements except for the last <var>count</var> resources from a nested resource
 collection.  This can be used in conjunction with the <a href="#sort">sort</a> collection, for
 example, to select all but the last few oldest, largest, etc. resources from a larger
 collection. <em>Since Ant 1.9.5</em></p>
 collection.</p>
 <table class="attr">
  <tr>
    <th>Attribute</th>
--- a/manual/inputhandler.html
+++ b/manual/inputhandler.html
@@ -87,16 +87,16 @@ define it as a simple parameter to <code>ant</code>, but you can
 define it inside the <code>ANT_OPTS</code> environment variable.</p>

 <h3>GreedyInputHandler</h3>

 <p><em>Since Ant 1.7</em></p>
 <p>Like the default implementation, this InputHandler reads from standard
 input. However, it consumes <em>all</em> available input. This behavior is
 useful for sending Ant input via an OS pipe. <em>Since Ant 1.7</em></p>
 useful for sending Ant input via an OS pipe.</p>

 <h3>SecureInputHandler</h3>

 <p><em>Since Ant 1.7.1</em></p>
 <p>This InputHandler calls <code>System.console().readPassword()</code>,
 available since Java 6.  On earlier platforms it falls back to the
 behavior of DefaultInputHandler. <em>Since Ant 1.7.1</em></p>
 behavior of DefaultInputHandler.</p>

 <h2>InputRequest</h2>

--- a/manual/listeners.html
+++ b/manual/listeners.html
@@ -503,6 +503,7 @@ are in charge&mdash;or, more importantly, which project is failing.
 <pre>ant -logger org.apache.tools.ant.listener.BigProjectLogger</pre>

 <h3 id="SimpleBigProjectLogger">SimpleBigProjectLogger</h3>
 <p><em>Since Ant 1.8.1</em></p>
 <p>Like <code>BigProjectLogger</code>, project-qualified target names
 are printed, useful for big builds with subprojects. Otherwise it is
 as quiet as <code>NoBannerLogger</code>:</p>
@@ -525,17 +526,16 @@ Building jar: /sources/myapp/build/myapp.jar

 BUILD SUCCESSFUL
 Total time: 1 second</pre>
 <p><em>since Ant 1.8.1</em></p>
 <p>To use this listener, use the command:</p>
 <pre>ant -logger org.apache.tools.ant.listener.SimpleBigProjectLogger</pre>

 <h3 id="ProfileLogger">ProfileLogger</h3>
 <!-- This is the 'since' as described in the Loggers JavaDoc -->
 <p><em>Since Ant 1.8.0</em></p>
 <p>This logger stores the time needed for executing a task, target and
 the whole build and prints these information. The output contains a
 timestamp when entering the build, target or task and a timestamp
 and the needed time when exiting.</p>
 <!-- This is the 'since' as described in the Loggers JavaDoc -->
 <p><em>since Ant 1.8.0</em></p>
 <h4>Example</h4>
 Having that buildfile
 <pre>
--- a/manual/proxy.html
+++ b/manual/proxy.html
@@ -57,7 +57,8 @@
  tell Ant on a Java 5+ system to have the JVM work it out for itself.
 </p>

 <h3>Java 5+ proxy support (<em>since Ant 1.7</em>)</h3>
 <h3>Java 5+ proxy support</h3>
 <p><em>Since Ant 1.7</em></p>
 <p>
  When Ant starts up, if the <code>-autoproxy</code> command is
  supplied, Ant sets the <code>java.net.useSystemProxies</code> system
--- a/manual/targets.html
+++ b/manual/targets.html
@@ -232,7 +232,7 @@

  <h1 id="extension-points">Extension-Points</h1>

  <p><em>since Ant 1.8.0</em>.</p>
  <p><em>Since Ant 1.8.0</em>.</p>

  <p>Extension-Points are similar to targets in that they have a name
    and a <var>depends</var> list and can be executed from the command