Consistent markup

manual/Tasks/ant.html

@@ -124,7 +124,7 @@ outside of targets in the new project—but not those defined inside of targ
 <h3>Parameters specified as nested elements</h3>
 
 <h4>property</h4>
-<p>See the description of the <a href="property.html">property</a> task.<br>  These properties
+<p>See the description of the <a href="property.html">property</a> task.<br/>  These properties
 become equivalent to properties you define on the command line. These are special properties and
 they will always get passed down, even through additional <code>&lt;*ant*&gt;</code> tasks
 with <var>inheritAll</var> set to <q>false</q> (see above).<br/>  Note that the <var>refid</var>

manual/Tasks/antcall.html

@@ -100,7 +100,7 @@ the <var>id</var> attribute).</p>
 <h3>Parameters specified as nested elements</h3>
 <h4>param</h4>
 <p>Specifies the properties to set before running the specified
-target. See <a href="property.html">property</a> for usage guidelines.<br>  These properties become
+target. See <a href="property.html">property</a> for usage guidelines.<br/>  These properties become
 equivalent to properties you define on the command line. These are special properties and they will
 always get passed down, even through additional <code>&lt;*ant*&gt;</code> tasks
 with <var>inheritAll</var> set to <q>false</q> (see above).</p>

manual/Tasks/antlr.html

@@ -72,13 +72,14 @@ the <code>antlr-all.jar</code> target of the Makefile provided with the download
   </tr>
   <tr>
     <td>html</td>
-    <td>Emit an HTML version of the grammar with hyperlinked actions.</td>
-    <td>No</td>
+    <td>Emit an HTML version of the grammar with hyperlinked actions if set to <q>yes</q>.</td>
+    <td>No; default is <q>no</q></td>
   </tr>
   <tr>
     <td>diagnostic</td>
-    <td>Generate a text file with debugging information based on the target grammar.</td>
-    <td>No</td>
+    <td>Generate a text file with debugging information based on the target grammar if set
+      to <q>yes</q>.</td>
+    <td>No; default is <q>no</q></td>
   </tr>
   <tr>
     <td>trace</td>

manual/Tasks/apply.html

@@ -72,7 +72,7 @@ standard input.</p>
   </tr>
   <tr>
     <td>spawn</td>
-    <td>whether or not you want the commands to be spawned.<br>  If you spawn a command, its output
+    <td>whether or not you want the commands to be spawned.<br/>  If you spawn a command, its output
     will not be logged by Ant.<br/>  The input, output, error, and result property settings are not
     active when spawning a process.<br/>  <em>since Ant 1.6</em></td>
     <td>No; default is <q>false</q></td>
@@ -175,8 +175,8 @@ standard input.</p>
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other than 0.</td>
-    <td>No</td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q>.</td>
+    <td>No; defaults to <q>false</q></td>
   </tr>
   <tr>
     <td>failifexecutionfails</td>
@@ -200,7 +200,7 @@ standard input.</p>
     <td>type</td>
     <td>One of <q>file</q>, <q>dir</q> or <q>both</q>. If set to <q>file</q>, only the names of
       plain files will be sent to the command. If set to <q>dir</q>, only the names of directories
-      are considered.<br>
+      are considered.<br/>
       <strong>Note</strong>: The <var>type</var> attribute does not apply to
       nested <code>dirset</code>s&mdash;<code>dirset</code>s always implicitly assume type to
       be <q>dir</q>.</td>

manual/Tasks/changelog.html

@@ -74,8 +74,7 @@ operation may fail when using such an incompatible client.</p>
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other
-      than <code>0</code></td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q></td>
     <td>No; defaults to <q>false</q></td>
   </tr>
   <tr>

manual/Tasks/checksum.html

@@ -92,7 +92,7 @@ Architecture Standard Algorithm Name Documentation</a></p>
       the <var>verifyproperty</var> attribute, property specifies the name of the property to be set
       with the generated checksum value.<br/><strong>If you set</strong>
       the <var>verifyproperty</var> attribute, property specifies the checksum you expect to be
-      generated (the checksum itself, not a name of a property containing the checksum).<br>  This
+      generated (the checksum itself, not a name of a property containing the checksum).<br/>  This
       cannot be specified when <var>fileext</var> is being used or when the number of files for
       which checksums are to be generated is greater than 1.
     </td>

manual/Tasks/clearcase.html

@@ -24,10 +24,10 @@
 
 <body>
 <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>
-Rob Anderson (Anderson.Rob at vectorscm dot com), and<br>
+<p>by:<br/>
+Curtis White (cwhite at aracnet dot com),<br/>
+Sean P. Kane (spkane at genomatica dot com),<br/>
+Rob Anderson (Anderson.Rob at vectorscm dot com), and<br/>
 Sean Egan    (sean at cm-logic dot com)</p>
 
 <p>Version 1.6&mdash;02/25/2003</p>
@@ -189,12 +189,11 @@ original.</p>
     <td>notco</td>
     <td>Fail if it's already checked out to the current view. Set to <q>false</q> to ignore
     it.<br/><em>Since Ant 1.6.1</em></td>
-    <td>No</td>
+    <td>No; default is <q>true</q></td>
   </tr>
   <tr>
     <td>failonerr</td>
-    <td>Throw an exception if the command fails.<br>
-    <em>Since Ant 1.6.1</em></td>
+    <td>Throw an exception if the command fails.<br/><em>Since Ant 1.6.1</em></td>
     <td>No; default is <q>true</q></td>
   </tr>
 </table>
@@ -375,8 +374,7 @@ set to the current time.</p>
   </tr>
   <tr>
     <td>failonerr</td>
-    <td>Throw an exception if the command fails.<br>
-    <em>Since Ant 1.6.1</em></td>
+    <td>Throw an exception if the command fails.<br/><em>Since Ant 1.6.1</em></td>
     <td>No; default is <q>true</q></td>
   </tr>
 </table>
@@ -845,8 +843,8 @@ automatically check it out.</p>
 
 <h2 id="ccmkelem">CCMkelem</h2>
 <h3>Description</h3>
-Task to perform a <code>cleartool mkelem</code> command to ClearCase.<br>
-<em>Since Ant 1.6.1</em>
+<p>Task to perform a <code>cleartool mkelem</code> command to ClearCase.<br/><em>Since Ant
+1.6.1</em></p>
 <h3>Parameters</h3>
 <table class="attr">
   <tr>

manual/Tasks/cvs.html

@@ -107,8 +107,8 @@ for recommended workarounds.</p>
   </tr>
   <tr>
     <td>reallyquiet</td>
-    <td>suppress all messages. This is the same as
-      <code>-Q</code> on the command line.  <em>since Ant 1.6</em>.</td>
+    <td>suppress all messages. This is the same as <code>-Q</code> on the command line.  <em>since
+      Ant 1.6</em>.</td>
     <td>No; defaults to <q>false</q></td>
   </tr>
   <tr>
@@ -143,8 +143,7 @@ for recommended workarounds.</p>
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other
-      than <code>0</code>.</td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q>.</td>
     <td>No; defaults to <q>false</q></td>
   </tr>
 </table>

manual/Tasks/cvstagdiff.html

@@ -121,7 +121,7 @@ example—and some operation may fail when using such an incompatible client
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other than 0.</td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q>.</td>
     <td>No; defaults to <q>false</q></td>
   </tr>
 </table>
@@ -196,7 +196,7 @@ output. The following example illustrates how to generate a HTML report from the
 
 <h4>Output</h4>
 <p>The <var>cvsroot</var> and <var>package</var> attributes of the <code>tagdiff</code> element are
-new in Ant 1.6.<br>  Notes on <code>entry</code> attributes:</p>
+new in Ant 1.6.<br/>  Notes on <code>entry</code> attributes:</p>
 <table>
   <tr>
     <th>Attribute</th>

manual/Tasks/ejb.html

@@ -774,7 +774,7 @@ vendor's EJB container. The parameters for each supported deployment element are
 them to the final EJB jar file. JBoss has two deployment descriptors:</p>
 <ul>
   <li><samp>jboss.xml</samp></li>
-  <li>for container manager persistence:<br>
+  <li>for container manager persistence:
     <table>
       <tr><th>CMP version</th><th>File name</th></tr>
       <tr><td>CMP 1.0</td><td><samp>jaws.xml</samp></td></tr>
@@ -1193,7 +1193,7 @@ the <code>websphere.home</code> property (look at the examples below).</p>
     <td>No; defaults to <q>_ejbdeploy_temp</q></td>
   </tr>
   <tr>
-    <td>dbName<br>dbSchema</td>
+    <td>dbName<br/>dbSchema</td>
     <td>These options are passed to <code>ejbdeploy</code>.</td>
     <td>No</td>
   </tr>

manual/Tasks/fail.html

@@ -68,7 +68,7 @@ the element.</p>
 <p>As an alternative to the <var>if</var>/<var>unless</var> attributes, conditional failure can be
 achieved using a single nested <code>&lt;condition&gt;</code> element, which should contain exactly
 one core or custom condition.  For information about conditions,
-see <a href="conditions.html">here</a>.<br><em>Since Ant 1.6.2</em>
+see <a href="conditions.html">here</a>.<br/><em>Since Ant 1.6.2</em>
 </p>
 
 <h3>Examples</h3>

manual/Tasks/ftp.html

@@ -325,7 +325,7 @@ connection.</p>
       Icelandic FTP server might conceivably be specified
       as <q>jan|feb|mar|apr|ma&iacute;|j&uacute;n|j&uacute;l|&aacute;g&uacute;|sep|okt|n&oacute;v|des</q>.
       This attribute exists primarily to support languages not supported by
-      the <var>serverLanguageCode</var> attribute.<br><em>Since Ant 1.7</em></td>
+      the <var>serverLanguageCode</var> attribute.<br/><em>Since Ant 1.7</em></td>
     <td>No</td>
   </tr>
 </table>
@@ -358,8 +358,7 @@ connection.</p>
     </tr>
     <tr>
       <td><q>list</q></td>
-      <td>base directory from which files are listed<br>
-      </td>
+      <td>base directory from which files are listed</td>
       <td>the remote files located under the <var>remotedir</var> matching the include/exclude
         patterns of the <var>fileset</var></td>
     </tr>

manual/Tasks/jar.html

@@ -523,7 +523,7 @@ JDK 6 scripting interface:</p>
 <p>Here we want to create a <em>Multi-Release JAR File</em> according the
 specification <a target="_blank" href="http://openjdk.java.net/jeps/238">JEP 238</a>.  It defines on
 top of a JAR the possibility to place additional or overwriting classes in a jar, which are
-available according to the Java version you run.<br>  Basically it says, that you have to set the
+available according to the Java version you run.<br/>  Basically it says, that you have to set the
 manifest entry <code>Multi-Release: true</code> and place all additional or overwriting classes
 in <samp>META-INF/versions/<i>number</i>/package-structure</samp>,
 e.g. <samp>META-INF/versions/9/org/apache/ant/MyClass.class</samp></p>

manual/Tasks/java.html

@@ -129,7 +129,7 @@ because it tries to read from the standard input.</p>
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other than 0.</td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q>.</td>
     <td>No; default is <q>false</q> (see <a href="#failonerror">note</a>)</td>
   </tr>
   <tr>

manual/Tasks/javac.html

@@ -294,7 +294,7 @@ file will not get compiled even if a native header file generated for it would b
       command-line switch.  Valid feature versions are <q>1.3</q>, <q>1.4</q>, <q>1.5</q>
       or <q>5</q>, etc.  The attribute will be ignored by all implementations prior
       to <q>javac1.4</q> (or <q>modern</q> when Ant is not running in a JVM 1.3), <q>gcj</q>
-      and <q>jikes</q>.<br>  If you use this attribute together with <q>gcj</q> or <q>jikes</q>, you
+      and <q>jikes</q>.<br/>  If you use this attribute together with <q>gcj</q> or <q>jikes</q>, you
       must make sure that your version supports the <code>-source</code> (or <code>-fsource</code>
       for <code>gcj</code>) switch.</td>
     <td>No; by default, no <code>-source</code> argument will be used at all unless the magic
@@ -694,8 +694,8 @@ are <q>false</q>.</p>
   </tr>
   <tr>
     <td><code>build.compiler.fulldepend</code></td>
-    <td>Enable full dependency checking; see<br> the <code>+F</code> switch in the Jikes
-        manual.</td>
+    <td>Enable full dependency checking; see<br/> the <code>+F</code> switch in the Jikes
+      manual.</td>
     <td><q>false</q></td>
   </tr>
   <tr>

manual/Tasks/javadoc.html

@@ -398,7 +398,7 @@ with the <var>exclude</var> patterns of the <code>packageset</code> (and vice ve
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>Stop the build process if the command exits with a return code other than 0.</td>
+    <td>Stop the build process if the command exits with a return code other than <q>0</q>.</td>
     <td>all</td>
     <td>No</td>
   </tr>
@@ -490,7 +490,7 @@ with the <var>exclude</var> patterns of the <code>packageset</code> (and vice ve
   <tr>
     <td>postProcessGeneratedJavadocs</td>
     <td>Whether to post-process the generated javadocs in order to mitigate
-      CVE-2013-1571.  <em>Since Ant 1.9.2</em><br> There is a frame injection attack possible in
+      CVE-2013-1571.  <em>Since Ant 1.9.2</em><br/> There is a frame injection attack possible in
       javadocs generated by Oracle JDKs prior to Java 7 update 25
       (<a href="https://www.oracle.com/technetwork/java/javase/7u25-relnotes-1955741.html#jpi-upt"
       target="_blank">details</a>).  When this flag is set to <q>true</q>, Ant will check whether

manual/Tasks/mail.html

@@ -148,7 +148,7 @@ more information.</p>
   <tr>
     <td>charset</td>
     <td>Character set of the email.<br/>You can also set the <var>charset</var> in
-      the <code>message</code> nested element.<br>  These options are mutually exclusive.</td>
+      the <code>message</code> nested element.<br/>  These options are mutually exclusive.</td>
     <td>No</td>
   </tr>
   <tr>
@@ -230,7 +230,7 @@ can contain email addresses of the form:</p>
   <tr>
     <td>charset</td>
     <td>Character set of the message<br/>You can also set the <var>charset</var> as attribute of the
-      enclosing <code>mail</code> task.<br>  These options are mutually exclusive.</td>
+      enclosing <code>mail</code> task.<br/>  These options are mutually exclusive.</td>
     <td>No</td>
   </tr>
   <tr>

manual/Tasks/netrexxc.html

@@ -50,7 +50,7 @@ nested <code>&lt;include&gt;</code>, <code>&lt;exclude&gt;</code>
 and <code>&lt;patternset&gt;</code> elements.</p>
 <p>All attributes except <var>classpath</var>, <var>srcdir</var> and <var>destDir</var> are also
 available as properties in the form <code>ant.netrexxc.<i>attributename</i></code>,
-eg.<br/><code>&lt;property name="ant.netrexxc.verbose" value="noverbose"/&gt;</code><br> or from the
+eg.<br/><code>&lt;property name="ant.netrexxc.verbose" value="noverbose"/&gt;</code><br/> or from the
 command line as<br/><code>ant -Dant.netrexxc.verbose=noverbose ...</code></p>
 <p><strong>Note</strong>: This task depends on external libraries not included in the Apache Ant
 distribution. See <a href="../install.html#librarydependencies">Library Dependencies</a> for more

manual/Tasks/replaceregexp.html

@@ -61,14 +61,14 @@ the <a href="../Types/regexp.html#implementation">Regexp Type</a>.</p>
   <tr>
     <td>flags</td>
     <td>The flags to use when matching the regular expression.  For more information, consult the
-      Perl 5 syntax<br>
-      <q>g</q> : Global replacement.  Replace all occurrences found<br>
-      <q>i</q> : Case Insensitive.  Do not consider case in the match<br>
+      Perl 5 syntax<br/>
+      <q>g</q> : Global replacement.  Replace all occurrences found<br/>
+      <q>i</q> : Case Insensitive.  Do not consider case in the match<br/>
       <q>m</q> : Multiline.  Treat the string as multiple lines of input, using <q>^</q>
       and <q>$</q> as the start or end of any line, respectively, rather than start or end of
-      string.<br>
+      string.<br/>
       <q>s</q> : Singleline.  Treat the string as a single line of input, using <q>.</q> to match
-      any character, including a newline, which normally, it would not match.<br>
+      any character, including a newline, which normally, it would not match.
     </td>
     <td>No</td>
   </tr>
@@ -118,7 +118,7 @@ pattern.  You can use this element to refer to a previously defined substitution
 instance.</p>
 
 <pre>
-&lt;substitution id="id" expression="beta\1alpha"/&gt;<br>
+&lt;substitution id="id" expression="beta\1alpha"/&gt;<br/>
 &lt;substitution refid="id"/&gt;</pre>
 
 <h3>Examples</h3>
@@ -151,7 +151,7 @@ input</p>
 &lt;html&gt; &lt;body&gt;
  &lt;h1&gt; T E S T &lt;/h1&gt; &lt;/body&gt;&lt;/html&gt;</pre>
 
-<br><!-- small distance from code of the previous example -->
+<br/><!-- small distance from code of the previous example -->
 
 <pre>
 &lt;replaceregexp match="\\n" replace="${line.separator}" flags="g" byline="true"&gt;

manual/Tasks/rmic.html

@@ -107,7 +107,7 @@ documentation to learn how to use it.</p>
     <td>stubversion</td>
     <td>Specify the JDK version for the generated stub code.  Specify <q>1.1</q> to pass
       the <code>-v1.1</code> option to <code>rmic</code>, <q>1.2</q>
-      for <code>-v12</code>, <q>compat</q> for <code>-vcompat</code>.<br>/<em>Since Ant 1.7</em>, if
+      for <code>-v12</code>, <q>compat</q> for <code>-vcompat</code>.<br/><em>Since Ant 1.7</em>, if
       you do not specify a version, and do not ask for <samp>.iiop</samp> or <samp>.idl</samp>
       files, <q>compat</q> is selected.</td>
     <td>No; default is <q>compat</q></td>

manual/Tasks/rpm.html

@@ -48,7 +48,7 @@ with <code>rpm</code> support.</p>
     <td>This is the directory which will have the expected
       subdirectories, <samp>SPECS</samp>, <samp>SOURCES</samp>, <samp>BUILD</samp>, <samp>SRPMS</samp>.
       If this isn't specified, the default RPM directory of the system (or user,
-      if <samp>~/.rpmmacros</samp> defines it) is used (often <samp>/usr/src/rpm</samp>.<br>
+      if <samp>~/.rpmmacros</samp> defines it) is used (often <samp>/usr/src/rpm</samp>.<br/>
       Defining a <var>topdir</var> will set <code>%_topdir</code> to the specified
       directory&mdash;there is no need to edit your <samp>.rpmmacros</samp> file.</td>
     <td>No, but your build file is very brittle if it is not set.</td>

manual/Tasks/schemavalidate.html

@@ -71,7 +71,7 @@ their URL equivalents.</p>
   <tr>
     <td>classpathref</td>
     <td>where to find the parser class.  Optionally can use an
-    embedded <code>&lt;classpath&gt;</code> element.</td>
+      embedded <code>&lt;classpath&gt;</code> element.</td>
     <td>No</td>
   </tr>
   <tr>
@@ -82,8 +82,8 @@ their URL equivalents.</p>
   </tr>
   <tr>
     <td>failonerror</td>
-    <td>fails on a error if set to <q>true</q> (defaults to <q>true</q>).</td>
-    <td>No</td>
+    <td>fails on a error if set to <q>true</q>.</td>
+    <td>No; defaults to <q>true</q></td>
   </tr>
   <tr>
     <td>file</td>
@@ -167,9 +167,9 @@ their URL equivalents.</p>
 <p>The <a href="../Types/xmlcatalog.html"><code>&lt;xmlcatalog&gt;</code></a> element is used to
 perform entity resolution.</p>
 <h4>attribute</h4>
-<p>The <code>&lt;attribute&gt;</code> element is used to set parser features.<br>Features usable
+<p>The <code>&lt;attribute&gt;</code> element is used to set parser features.<br/>Features usable
 with the xerces parser are defined
-here: <a href="https://xml.apache.org/xerces-j/features.html">Setting features</a><br>SAX features
+here: <a href="https://xml.apache.org/xerces-j/features.html">Setting features</a><br/>SAX features
 are defined
 here: <a href="http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html#package_description"><code>http://xml.org/sax/features/</code></a></p>
 <table class="attr">

manual/Tasks/script.html

@@ -41,7 +41,7 @@ either their <var>name</var> or <var>id</var> attributes (as long as their names
 valid Java identifiers, that is).  This is controlled by the <var>setbeans</var> attribute of the
 task.  The name <code>project</code> is a pre-defined reference to the Project, which can be used
 instead of the project name. The name <code>self</code> is a pre-defined reference to the
-actual <code>&lt;script&gt;</code>-Task instance.<br>From these objects you have access to the Ant
+actual <code>&lt;script&gt;</code>-Task instance.<br/>From these objects you have access to the Ant
 Java API, see the <a href="../api/index.html">JavaDoc</a> (especially
 for <a href="../api/org/apache/tools/ant/Project.html">Project</a>
 and <a href="../api/org/apache/tools/ant/taskdefs/optional/Script.html">Script</a>) for more
@@ -272,11 +272,11 @@ be imported
 with <code>importClass(<strong>Packages</strong>.org.apache.tools.ant.util.FileUtils)</code><br/>
 The <code>&lt;script&gt;</code> task populates the Project instance under the
 name <code>project</code>, so we can use that reference. Another way is to use its given name or
-getting its reference from the task itself.<br>  The Project provides methods for accessing and
-setting properties, creating DataTypes and Tasks and much more.<br>  After creating a FileSet object
+getting its reference from the task itself.<br/>  The Project provides methods for accessing and
+setting properties, creating DataTypes and Tasks and much more.<br/>  After creating a FileSet object
 we initialize that by calling its set-methods. Then we can use that object like a normal Ant task
-(<code>&lt;copy&gt;</code> for example).<br>  For getting the size of a file we instantiate
-a <code>java.io.File</code>. So we are using normal Java API here.<br>  Finally we use
+(<code>&lt;copy&gt;</code> for example).<br/>  For getting the size of a file we instantiate
+a <code>java.io.File</code>. So we are using normal Java API here.<br/>  Finally we use
 the <code>&lt;echo&gt;</code> task for producing the output. The task is not executed by
 its <code>execute()</code> method, because the <code>perform()</code> method (implemented in Task
 itself) does the appropriate logging before and after invoking <code>execute()</code>.</p>

manual/Tasks/sound.html

@@ -62,7 +62,7 @@ and <code>&lt;fail&gt;</code> elements:</p>
   <tr>
     <td>loops</td>
     <td>the number of extra times to play the sound file.</td>
-    <td>No; default is <code>0</code></td>
+    <td>No; default is <q>0</q></td>
   </tr>
   <tr>
     <td>duration</td>

manual/Tasks/sshsession.html

@@ -73,7 +73,7 @@ JSCh earlier than 0.1.28.</p>
   <tr>
     <td>remotetunnels</td>
     <td>A comma-delimited list of colon-delimited <samp>rport:lhost:lport</samp> triplets defining
-      remote port forwarding.<br>  If nested <a href="#RemoteTunnel">remotetunnel</a> elements are
+      remote port forwarding.<br/>  If nested <a href="#RemoteTunnel">remotetunnel</a> elements are
       also provided, both sets of tunnels will be established.</td>
     <td>No</td>
   </tr>

manual/Tasks/style.html

@@ -219,8 +219,8 @@ path-like structure).</p>
   <tr>
     <td>failOnError</td>
     <td>Whether the build should fail if any error occurs.  Note that transformation errors can
-      still be suppressed by setting <q>failOnTransformationError</q> to <q>false</q> even if this
-      attribute is <q>true</q>.  <em>Since Ant 1.8.0</em>.</td>
+      still be suppressed by setting <var>failOnTransformationError</var> to <q>false</q> even if
+      this attribute is <q>true</q>.  <em>Since Ant 1.8.0</em>.</td>
     <td>No; default is <q>true</q></td>
   </tr>
   <tr>

manual/Tasks/subant.html

@@ -77,8 +77,8 @@ directories.  2 different options are offered:</p>
   </tr>
   <tr>
     <td>genericantfile</td>
-    <td>Build file path, to use in conjunction with directories.<br>  Use <var>genericantfile</var>,
-      in order to run the same build file with different <var>basedir</var>s.<br>  If this attribute
+    <td>Build file path, to use in conjunction with directories.<br/>  Use <var>genericantfile</var>,
+      in order to run the same build file with different <var>basedir</var>s.<br/>  If this attribute
       is set, <var>antfile</var> is ignored.</td>
     <td class="left">File</td>
   </tr>

manual/Tasks/symlink.html

@@ -74,7 +74,7 @@ set of property files to create links from.</p>
   <tr>
     <td>failonerror</td>
     <td>Stop build if true, log a warning message, but do not stop the build, when the an error
-      occurs if false.</td>
+      occurs if <q>false</q>.</td>
     <td>No; defaults to <q>true</q></td>
   </tr>
 </table>

manual/Tasks/unzip.html

@@ -81,7 +81,7 @@ extract an Ant generated ZIP archive.</p>
   </tr>
   <tr>
     <td>compression</td>
-    <td><strong>Note</strong>: This attribute is only available for the <code>untar</code> task.<br>
+    <td><strong>Note</strong>: This attribute is only available for the <code>untar</code> task.<br/>
       compression method.  Allowable values are <q>none</q>, <q>gzip</q>, <q>xz</q>
       and <q>bzip2</q>.</td>
     <td>No; default is <q>none</q></td>
@@ -112,7 +112,7 @@ extract an Ant generated ZIP archive.</p>
   </tr>
   <tr>
     <td>scanForUnicodeExtraFields</td>
-    <td><strong>Note</strong>: This attribute is not available for the <code>untar</code> task.<br>
+    <td><strong>Note</strong>: This attribute is not available for the <code>untar</code> task.<br/>
       If the archive contains Unicode extra fields then use them to set the file names, ignoring the
       specified encoding.  <br/>See also the <a href="zip.html#encoding">discussion in the zip task
       page</a></td>

manual/Tasks/xmlproperty.html

@@ -127,7 +127,7 @@ the input XML file is loaded:/p>
   </tr>
   <tr>
     <td>delimiter</td>
-    <td>Delimiter for splitting multiple values.<br><em>since Apache Ant 1.7.1</em></td>
+    <td>Delimiter for splitting multiple values.<br/><em>since Apache Ant 1.7.1</em></td>
     <td>No; defaults to <q>,</q> (comma)</td>
   </tr>
 </table>

manual/Types/filterchain.html

@@ -82,34 +82,34 @@ also.</p>
   &lt;/filterchain&gt;
 &lt;/loadfile&gt;</pre>
 
-<p>The following built-in tasks support nested <code>&lt;filterchain&gt;</code> elements.<br>
-<a href="../Tasks/concat.html">Concat</a>,<br>
-<a href="../Tasks/copy.html">Copy</a>,<br>
-<a href="../Tasks/loadfile.html">LoadFile</a>,<br>
-<a href="../Tasks/loadproperties.html">LoadProperties</a>,<br>
-<a href="../Tasks/loadresource.html">LoadResource</a>,<br>
+<p>The following built-in tasks support nested <code>&lt;filterchain&gt;</code> elements.<br/>
+<a href="../Tasks/concat.html">Concat</a>,<br/>
+<a href="../Tasks/copy.html">Copy</a>,<br/>
+<a href="../Tasks/loadfile.html">LoadFile</a>,<br/>
+<a href="../Tasks/loadproperties.html">LoadProperties</a>,<br/>
+<a href="../Tasks/loadresource.html">LoadResource</a>,<br/>
 <a href="../Tasks/move.html">Move</a></p>
 
-<p>A FilterChain is formed by defining zero or more of the following nested elements.<br>
-<a href="#filterreader">FilterReader</a><br>
-<a href="#classconstants">ClassConstants</a><br>
-<a href="#escapeunicode">EscapeUnicode</a><br>
-<a href="#expandproperties">ExpandProperties</a><br>
-<a href="#headfilter">HeadFilter</a><br>
-<a href="#linecontains">LineContains</a><br>
-<a href="#linecontainsregexp">LineContainsRegExp</a><br>
-<a href="#prefixlines">PrefixLines</a><br>
-<a href="#replacetokens">ReplaceTokens</a><br>
-<a href="#stripjavacomments">StripJavaComments</a><br>
-<a href="#striplinebreaks">StripLineBreaks</a><br>
-<a href="#striplinecomments">StripLineComments</a><br>
-<a href="#suffixlines">SuffixLines</a><br>
-<a href="#tabstospaces">TabsToSpaces</a><br>
-<a href="#tailfilter">TailFilter</a><br>
-<a href="#deletecharacters">DeleteCharacters</a><br>
-<a href="#concatfilter">ConcatFilter</a><br>
-<a href="#sortfilter">SortFilter</a><br>
-<a href="#tokenfilter">TokenFilter</a><br>
+<p>A FilterChain is formed by defining zero or more of the following nested elements.<br/>
+<a href="#filterreader">FilterReader</a><br/>
+<a href="#classconstants">ClassConstants</a><br/>
+<a href="#escapeunicode">EscapeUnicode</a><br/>
+<a href="#expandproperties">ExpandProperties</a><br/>
+<a href="#headfilter">HeadFilter</a><br/>
+<a href="#linecontains">LineContains</a><br/>
+<a href="#linecontainsregexp">LineContainsRegExp</a><br/>
+<a href="#prefixlines">PrefixLines</a><br/>
+<a href="#replacetokens">ReplaceTokens</a><br/>
+<a href="#stripjavacomments">StripJavaComments</a><br/>
+<a href="#striplinebreaks">StripLineBreaks</a><br/>
+<a href="#striplinecomments">StripLineComments</a><br/>
+<a href="#suffixlines">SuffixLines</a><br/>
+<a href="#tabstospaces">TabsToSpaces</a><br/>
+<a href="#tailfilter">TailFilter</a><br/>
+<a href="#deletecharacters">DeleteCharacters</a><br/>
+<a href="#concatfilter">ConcatFilter</a><br/>
+<a href="#sortfilter">SortFilter</a><br/>
+<a href="#tokenfilter">TokenFilter</a><br/>
 <a href="../Tasks/fixcrlf.html">FixCRLF</a></p>
 
 <h3 id="filterreader">FilterReader</h3>
@@ -364,9 +364,8 @@ matching strings.</p>
   </tr>
   <tr>
     <td>regexp</td>
-    <td>Regular expression to be searched for.<br>
-      <em>Since Ant 1.10.2</em>, this also works as an attribute
-      on <code>linecontainsregexp</code>. In earlier versions of Ant you must use a nested
+    <td>Regular expression to be searched for.<br/><em>Since Ant 1.10.2</em>, this also works as an
+      attribute on <code>linecontainsregexp</code>. In earlier versions of Ant you must use a nested
       element when using the convenience method.
     </td>
     <td>Yes</td>
@@ -1093,25 +1092,25 @@ following are understood: <q>\n</q>, <q>\r</q>, <q>\f</q>, <q>\t</q> and <q>\\</
 </table>
 <p>The following tokenizers are provided by the default distribution.</p>
 <p>
-  <a href="#linetokenizer">LineTokenizer</a><br>
-  <a href="#filetokenizer">FileTokenizer</a><br>
-  <a href="#stringtokenizer">StringTokenizer</a><br>
+  <a href="#linetokenizer">LineTokenizer</a><br/>
+  <a href="#filetokenizer">FileTokenizer</a><br/>
+  <a href="#stringtokenizer">StringTokenizer</a>
 </p>
 <p>The following string filters are provided by the default distribution.</p>
 <p>
-  <a href="#replacestring">ReplaceString</a><br>
-  <a href="#containsstring">ContainsString</a><br>
-  <a href="#replaceregex">ReplaceRegex</a><br>
-  <a href="#containsregex">ContainsRegex</a><br>
-  <a href="#trim">Trim</a><br>
-  <a href="#ignoreblank">IgnoreBlank</a><br>
-  <a href="#filterdeletecharacters">DeleteCharacters</a><br>
-  <a href="#uniqfilter">UniqFilter</a><br>
-  <a href="#native2asciifilter">Native2AsciiFilter</a><br>
+  <a href="#replacestring">ReplaceString</a><br/>
+  <a href="#containsstring">ContainsString</a><br/>
+  <a href="#replaceregex">ReplaceRegex</a><br/>
+  <a href="#containsregex">ContainsRegex</a><br/>
+  <a href="#trim">Trim</a><br/>
+  <a href="#ignoreblank">IgnoreBlank</a><br/>
+  <a href="#filterdeletecharacters">DeleteCharacters</a><br/>
+  <a href="#uniqfilter">UniqFilter</a><br/>
+  <a href="#native2asciifilter">Native2AsciiFilter</a>
 </p>
 <p>The following string filters are provided by the optional distribution.</p>
 <p>
-  <a href="#scriptfilter">ScriptFilter</a><br>
+  <a href="#scriptfilter">ScriptFilter</a>
 </p>
 <p>
   <a href="#custom">Custom</a> tokenizers and string filters can be declared

manual/Types/selectors-program.html

@@ -192,7 +192,7 @@ public class MySelectorTest {
     <p>During development and maybe later you sometimes need the output of information.
     Therefore Logging is needed. Because the selector extends BaseExtendSelector or directly
     BaseSelector it is an Ant <code>DataType</code> and therefore
-    a <code>ProjectComponent</code>.<br>  That means that you have access to the project object
+    a <code>ProjectComponent</code>.<br/>  That means that you have access to the project object
     and its logging capability.  <code>ProjectComponent</code> itself
     provides <code>log()</code> methods which will do the access to the project
     instance. Logging is therefore done simply with:</p>

manual/develop.html

@@ -506,7 +506,7 @@ been configured.</p>
 <h3>Example</h3>
 Writing an adapter to your favourite log library is very easy.
 Just implement the BuildListener interface, instantiate your logger and delegate
-the message to that instance.<br>
+the message to that instance.<br/>
 When starting your build provide your adapter class and the log library to the
 build classpath and activate your logger via <code>-listener</code> option as
 described above.

manual/dirtasks.html

@@ -143,7 +143,7 @@ were <samp>mypackage/test/**</samp>.</p>
     <td><samp>**/CVS/*</samp></td>
     <td>Matches all files in <samp>CVS</samp>
       directories that can be located
-      anywhere in the directory tree.<br>
+      anywhere in the directory tree.<br/>
       Matches:
 <pre>
 CVS/Repository
@@ -157,7 +157,7 @@ But not:
   <tr>
     <td><samp>org/apache/jakarta/**</samp></td>
     <td>Matches all files in the <samp>org/apache/jakarta</samp>
-      directory tree.<br>
+      directory tree.<br/>
       Matches:
 <pre>
 org/apache/jakarta/tools/ant/docs/index.html
@@ -171,7 +171,7 @@ But not:
     <td><samp>org/apache/**/CVS/*</samp></td>
     <td>Matches all files in <samp>CVS</samp> directories
       that are located anywhere in the directory tree under
-      <samp>org/apache</samp>.<br>
+      <samp>org/apache</samp>.<br/>
       Matches:
 <pre>
 org/apache/CVS/Entries

manual/running.html

@@ -489,7 +489,7 @@ your build file.
 <p>
 Ant start up scripts (in their Windows and Unix version) return the
 return code of the <code>java</code> program. So a successful build
-returns 0, failed builds return other values.
+returns <q>0</q>, failed builds return other values.
 </p>
 
 <h2 id="cygwin">Cygwin Users</h2>

manual/tasksoverview.html

@@ -29,23 +29,23 @@ difficult to get an overall view of what each task can do.  The following
 tables provide a short description of each task and a link to the complete
 documentation.</p>
 
-<a href="#archive">Archive Tasks</a><br>
-<a href="#audit">Audit/Coverage Tasks</a><br>
-<a href="#compile">Compile Tasks</a><br>
-<a href="#deploy">Deployment Tasks</a><br>
-<a href="#doc">Documentation Tasks</a><br>
-<a href="#ejb">EJB Tasks</a><br>
-<a href="#exec">Execution Tasks</a><br>
-<a href="#file">File Tasks</a><br>
-<a href="#extensions">Java Extensions Tasks</a><br>
-<a href="#log">Logging Tasks</a><br>
-<a href="#mail">Mail Tasks</a><br>
-<a href="#misc">Miscellaneous Tasks</a><br>
-<a href="#preproc">Pre-process Tasks</a><br>
-<a href="#prop">Property Tasks</a><br>
-<a href="#remote">Remote Tasks</a><br>
-<a href="#scm">SCM Tasks</a><br>
-<a href="#testing">Testing Tasks</a><br>
+<a href="#archive">Archive Tasks</a><br/>
+<a href="#audit">Audit/Coverage Tasks</a><br/>
+<a href="#compile">Compile Tasks</a><br/>
+<a href="#deploy">Deployment Tasks</a><br/>
+<a href="#doc">Documentation Tasks</a><br/>
+<a href="#ejb">EJB Tasks</a><br/>
+<a href="#exec">Execution Tasks</a><br/>
+<a href="#file">File Tasks</a><br/>
+<a href="#extensions">Java Extensions Tasks</a><br/>
+<a href="#log">Logging Tasks</a><br/>
+<a href="#mail">Mail Tasks</a><br/>
+<a href="#misc">Miscellaneous Tasks</a><br/>
+<a href="#preproc">Pre-process Tasks</a><br/>
+<a href="#prop">Property Tasks</a><br/>
+<a href="#remote">Remote Tasks</a><br/>
+<a href="#scm">SCM Tasks</a><br/>
+<a href="#testing">Testing Tasks</a><br/>
 
 <div class="float" id="archive">
     <span class="left">Archive Tasks</span>

manual/tutorial-HelloWorldWithAnt.html

@@ -464,7 +464,7 @@ steps: 1. let <code>&lt;junit&gt;</code> log the information and 2. convert thes
 define a report directory, create it before running the <q>junit</q> and redirect the logging to it. The log format is
 XML so <q>junitreport</q> could parse it. In a second target <q>junitreport</q> should create a browsable HTML report
 for all generated XML log files in the report directory. Now you can open the <samp>${report.dir}\index.html</samp> and
-see the result (looks something like JavaDoc).<br>  Personally I use two different targets
+see the result (looks something like JavaDoc).<br/>  Personally I use two different targets
 for <code>&lt;junit&gt;</code> and <code>&lt;junitreport&gt;</code>. Generating the HTML report needs some time and you
 don't need the HTML report just for testing, e.g. if you are fixing an error or a integration server is doing a job.</p>
 

manual/using.html

@@ -515,26 +515,26 @@ For the declaration there are several ways:
   <li>declare a single task per using instruction using
       <code>&lt;<a href="Tasks/taskdef.html">taskdef</a> name=&quot;taskname&quot;
       classname=&quot;ImplementationClass&quot;/&gt;</code>
-      <br>
+      <br/>
       <code>&lt;taskdef name=&quot;for&quot; classname=&quot;net.sf.antcontrib.logic.For&quot;/&gt;
       &lt;for ... /&gt;</code>
   </li>
   <li>declare a bundle of tasks using a <samp>properties</samp> file holding these
       taskname-ImplementationClass-pairs and <code>&lt;taskdef&gt;</code>
-      <br>
+      <br/>
       <code>&lt;taskdef resource=&quot;net/sf/antcontrib/antcontrib.properties&quot;/&gt;
       &lt;for ... /&gt;</code>
   </li>
   <li>declare a bundle of tasks using
       an <a href="Types/antlib.html">xml file</a> holding these
       taskname-ImplementationClass-pairs and <code>&lt;taskdef&gt;</code>
-      <br>
+      <br/>
       <code>&lt;taskdef resource=&quot;net/sf/antcontrib/antlib.xml&quot;/&gt;
       &lt;for ... /&gt;</code>
   </li>
   <li>declare a bundle of tasks using an xml file named <samp>antlib.xml</samp>, XML namespace and
       <a href="Types/antlib.html#antlibnamespace"><code>antlib:</code> protocol handler</a>
-      <br>
+      <br/>
       <code>&lt;project xmlns:ac=&quot;antlib:net.sf.antcontrib&quot;/&gt;
       &lt;ac:for ... /&gt;</code>
   </li>