You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by gi...@apache.org on 2018/01/23 18:02:30 UTC
[2/7] ant git commit: Reviewed documentation: - stripped trailing
whitespace; - corrected the tag soup;
- corrected Java versions (1.4 followed by 5);
- stripped inline styling (use CSS for uniformity).
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/schemavalidate.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/schemavalidate.html b/manual/Tasks/schemavalidate.html
index 1aac2ef..a29a414 100644
--- a/manual/Tasks/schemavalidate.html
+++ b/manual/Tasks/schemavalidate.html
@@ -23,7 +23,7 @@
<body>
-<h2><a name="schemavalidate">SchemaValidate</a></h2>
+<h2 id="schemavalidate">SchemaValidate</h2>
<h3>Description</h3>
<p>This <tt>schemavalidate</tt> task validates XML files described by an XML Schema.
@@ -42,7 +42,8 @@ Note that nested catalogs are still used for lookup of the URLs given as the
sources of schema documents, so you can still delegate lookup to a catalog, you
just need to list all schema URIs and their URL equivalents.
-<p>This task supports the use of nested
+<p>This task supports the use of nested</p>
+<ul>
<li><a href="../Types/xmlcatalog.html"><tt><xmlcatalog></tt></a> elements</li>
<li> <tt><schema></tt> elements, that bind a namespace URI to a URL or a
local filename.
@@ -51,16 +52,16 @@ just need to list all schema URIs and their URL equivalents.
These can be any number of
<a href="http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html#package_description"><tt>http://xml.org/sax/features/</tt></a>
or other features that your parser may support.</li>
- <li><tt><property></tt> elements, containing string properties
-</p>
+<li><tt><property></tt> elements, containing string properties</li>
+</ul>
<p>
The task only supports SAX2 or later parsers: it is an error to specify a SAX1
-parser.
-
+parser.
+</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -73,14 +74,14 @@ parser.
</tr>
<tr>
<td valign="top">classpathref</td>
- <td valign="top">where to find the parser class.
+ <td valign="top">where to find the parser class.
Optionally can use an embedded <tt><classpath></tt> element.</td>
<td align="center" valign="top">No</td>
</tr>
<tr>
<td valign="top">disableDTD</td>
<td valign="top">
- Flag to disable DTD support. DTD support is needed to
+ Flag to disable DTD support. DTD support is needed to
validate XSD files themselves, amongst others.
</td>
<td valign="top" align="center">No - default false</td>
@@ -102,7 +103,7 @@ parser.
</td>
<td valign="top" align="center">No - default true</td>
</tr>
-
+
<tr>
<td valign="top">lenient</td>
<td valign="top">
@@ -113,7 +114,7 @@ parser.
<tr>
<td valign="top">noNamespaceFile</td>
<td valign="top">
- filename of a no-namespace XSD file to provide the
+ filename of a no-namespace XSD file to provide the
schema for no-namespace XML content.
</td>
<td valign="top" align="center">No</td>
@@ -121,7 +122,7 @@ parser.
<tr>
<td valign="top">noNamespaceURL</td>
<td valign="top">
- URL of a no-namespace XSD file to provide the
+ URL of a no-namespace XSD file to provide the
schema for no-namespace XML content.
</td>
<td valign="top" align="center">No</td>
@@ -133,15 +134,14 @@ parser.
</tr>
</table>
-<h3><a name="nested">Nested Elements</a></h3>
-
+<h3 id="nested">Nested Elements</h3>
<h4>schema</h4>
<p>
Identify the name and location of a schema that may be used in validating
the document(s).
</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
<td width="78%" valign="top"><b>Description</b></td>
@@ -168,7 +168,7 @@ the document(s).
<p>
<tt><dtd></tt> is used to specify different locations for DTD resolution.
</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
<td width="78%" valign="top"><b>Description</b></td>
@@ -197,7 +197,7 @@ Features usable with the xerces parser are defined here :
SAX features are defined here:
<a href="http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html#package_description"><tt>http://xml.org/sax/features/</tt></a><br>
</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
<td width="78%" valign="top"><b>Description</b></td>
@@ -214,7 +214,6 @@ SAX features are defined here:
<td align="center" valign="top">Yes</td>
</tr>
</table>
-</p>
<h4>property</h4>
<p>The <tt><property></tt> element is used to set properties.
@@ -222,7 +221,7 @@ These properties are defined here for the xerces XML parser implementation :
<a href="http://xml.apache.org/xerces-j/properties.html">XML Parser properties</a>
Properties can be used to set the schema used to validate the XML file.
</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
<td width="78%" valign="top"><b>Description</b></td>
@@ -239,8 +238,6 @@ Properties can be used to set the schema used to validate the XML file.
<td align="center" valign="top">Yes</td>
</tr>
</table>
-</p>
-
<h3>Examples</h3>
<pre>
@@ -250,7 +247,7 @@ Properties can be used to set the schema used to validate the XML file.
</schemavalidate>
</pre>
Validate a document against an XML schema. The document does not declare
-any schema itself, which is why the <tt>noNamespaceFile</tt> is needed.
+any schema itself, which is why the <tt>noNamespaceFile</tt> is needed.
<pre>
<presetdef name="validate-soap">
<schemavalidate>
@@ -266,18 +263,16 @@ any schema itself, which is why the <tt>noNamespaceFile</tt> is needed.
</presetdef>
</pre>
Declare a new preset task, <tt><validate-soap></tt>, that validates
-XSD and WSDL documents against the relevant specifications.
-To validate XSD documents, you also need XMLSchema.dtd and datatypes.dtd in
+XSD and WSDL documents against the relevant specifications.
+To validate XSD documents, you also need XMLSchema.dtd and datatypes.dtd in
the same directory as XMLSchema.xsd, or pointed to via the catalog. All
these files can be fetched from <a href="http://www.w3.org/2001/XMLSchema">
-the W3C</a>.
+the W3C</a>.
<pre>
<validate-soap file="xml/test.xsd"/>
</pre>
Use the preset task defined above to validate an XML Schema document.
<br>
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/scp.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/scp.html b/manual/Tasks/scp.html
index 47a3cee..173b1b8 100644
--- a/manual/Tasks/scp.html
+++ b/manual/Tasks/scp.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="scp">SCP</a></h2>
+<h2 id="scp">SCP</h2>
<h3>Description</h3>
<p><em>since Apache Ant 1.6</em></p>
@@ -41,7 +41,7 @@ for more information. This task has been tested with jsch-0.1.2 and later.</p>
<p>See also the <a href="sshexec.html">sshexec task</a></p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -81,7 +81,7 @@ for more information. This task has been tested with jsch-0.1.2 and later.</p>
authentication or specify the password attribute. The way remote
path is recognized is whether it contains @ character or not. This
will not work if your localPath contains @ character.</td>
- <td valian="top" align="center">Yes</td>
+ <td valign="top" align="center">Yes</td>
</tr>
<tr>
<td valign="top">localTodir</td>
@@ -90,33 +90,33 @@ for more information. This task has been tested with jsch-0.1.2 and later.</p>
reason this was added was that when you give todir attribute it is
treated as remote if it contains @ character. This character can
exist also in local paths. <em>since Ant 1.6.2</em></td>
- <td valian="top" align="center">Alternative to todir attribute.</td>
+ <td valign="top" align="center">Alternative to todir attribute.</td>
</tr>
<tr>
<td valign="top">localTofile</td>
<td valign="top">Changes the file name to the given name while
receiving it, only useful if receiving a single file. <em>since
Ant 1.6.2</em></td>
- <td valian="top" align="center">Alternative to todir attribute.</td>
+ <td valign="top" align="center">Alternative to todir attribute.</td>
</tr>
<tr>
<td valign="top">remoteTodir</td>
<td valign="top">This is an alternative to the todir
attribute. But this must always point to a remote directory.
<em>since Ant 1.6.2</em></td>
- <td valian="top" align="center">Alternative to todir attribute.</td>
+ <td valign="top" align="center">Alternative to todir attribute.</td>
</tr>
<tr>
<td valign="top">remoteTofile</td>
<td valign="top">Changes the file name to the given name while
sending it, only useful if sending a single file. <em>since
Ant 1.6.2</em></td>
- <td valian="top" align="center">Alternative to todir attribute.</td>
+ <td valign="top" align="center">Alternative to todir attribute.</td>
</tr>
<tr>
<td valign="top">port</td>
<td valign="top">The port to connect to on the remote host.</td>
- <td valian="top" align="center">No, defaults to 22.</td>
+ <td valign="top" align="center">No, defaults to 22.</td>
</tr>
<tr>
<td valign="top">trust</td>
@@ -124,14 +124,14 @@ for more information. This task has been tested with jsch-0.1.2 and later.</p>
<strong>Note</strong> If you set this to false (the default), the
host you connect to must be listed in your knownhosts file, this
also implies that the file exists.</td>
- <td valian="top" align="center">No, defaults to No.</td>
+ <td valign="top" align="center">No, defaults to No.</td>
</tr>
<tr>
<td valign="top">knownhosts</td>
<td valign="top">This sets the known hosts file to use to validate
the identity of the remote host. This must be a SSH2 format file.
SSH1 format is not supported.</td>
- <td valian="top" align="center">No, defaults to
+ <td valign="top" align="center">No, defaults to
${user.home}/.ssh/known_hosts.</td>
</tr>
<tr>
@@ -248,10 +248,9 @@ password attribute</b></p>
authentication.</b></p>
<pre>
<scp file="myfile.txt"
- todir="user@somehost:/home/chuck"
+ todir="user@somehost:/home/chuck"
keyfile="${user.home}/.ssh/id_dsa"
- passphrase="my extremely secret passphrase"
- />
+ passphrase="my extremely secret passphrase"/>
</pre>
<p><b>Copy a single remote file to a local directory</b></p>
@@ -299,17 +298,16 @@ substitution and include the password on the command line. For example:
<pre>
<scp todir="${username}:${password}@host:/dir" ...>
</pre>
-Invoking ant with the following command line:
+Invoking Ant with the following command line:
<pre>
ant -Dusername=me -Dpassword=mypassword target1 target2
</pre>
-
+<p>
Is slightly better, but the username/password is exposed to all users on an Unix
system (via the ps command). The best approach is to use the
<code><input></code> task and/or retrieve the password from a (secured)
.properties file.
-
-<p>
+</p>
<p><strong>Unix Note:</strong> File permissions are not retained when files
are downloaded; they end up with the default <code>UMASK</code> permissions
@@ -319,8 +317,5 @@ preserving copy function, use <code><exec executable="scp" ... ></code>
instead.
</p>
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/script.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/script.html b/manual/Tasks/script.html
index d111124..ff8478d 100644
--- a/manual/Tasks/script.html
+++ b/manual/Tasks/script.html
@@ -17,14 +17,14 @@
<html>
<head>
-<meta http-equiv="Content-Language" content="en-us"></meta>
+<meta http-equiv="Content-Language" content="en-us">
<link rel="stylesheet" type="text/css" href="../stylesheets/style.css">
<title>Script Task</title>
</head>
<body>
-<h2><a name="script">Script</a></h2>
+<h2 id="script">Script</h2>
<h3>Description</h3>
<p>Execute a script in a
<a href="http://jakarta.apache.org/bsf" target="_top">Apache BSF</a>
@@ -38,7 +38,7 @@
</p>
<p>
The task may use the BSF scripting manager or the JSR 223 manager that
- is included in JDK6 and higher. This is controlled by the <code>manager</code>
+ is included in JDK 6 and higher. This is controlled by the <code>manager</code>
attribute. The JSR 223 scripting manager is indicated by "javax".
</p>
<p>All items (tasks, targets, etc) of the running project are
@@ -67,7 +67,7 @@ Location to a useful value. In particular all targets should have
different location values.</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -82,18 +82,18 @@ different location values.</p>
<tr>
<td valign="top">manager</td>
<td valign="top">
- <em>Since: Ant 1.7. </em>
+ <em>Since: Ant 1.7.</em>
The script engine manager to use. This can have
one of three values ("auto", "bsf" or "javax").
The default value is "auto".
- <dl>
+ <ul>
<li>"bsf" use the BSF scripting manager to run
the language.</li>
<li>"javax" use the <em>javax.scripting</em> manager
- to run the language. (This will only work for JDK6 and higher).</li>
+ to run the language. (This will only work for JDK 6 and higher).</li>
<li>"auto" use the BSF engine if it exists,
otherwise use the <em>javax.scripting</em> manager.</li>
- </dl>
+ </ul>
</td>
<td valign="top" align="center">No</td>
</tr>
@@ -137,13 +137,14 @@ different location values.</p>
<h4>classpath</h4>
<p><em>Since Ant 1.7</em></p>
<p>
- <code>Script</code>'s <code>classpath</code> attribute is a
+ <code>Script</code>'s <code>classpath</code> 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>
<p>
If a classpath is set, it will be used as the current thread
context classloader, and
- as the classloader given to the BSF manager.
+ as the classloader given to the BSF manager.
This means that it can be used to specify
the classpath containing the language implementation for BSF
or for JSR 223 managers.
@@ -159,7 +160,6 @@ different location values.</p>
that have engines in the BSF jar file. This includes the
javascript, jython, netrexx and jacl languages.
</p>
-</p>
<h3>Examples</h3>
The following snippet shows use of five different languages:
<blockquote><pre>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/scriptdef.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/scriptdef.html b/manual/Tasks/scriptdef.html
index f593e61..a102891 100644
--- a/manual/Tasks/scriptdef.html
+++ b/manual/Tasks/scriptdef.html
@@ -24,11 +24,11 @@
<body>
-<h2><a name="script">Scriptdef</a></h2>
+<h2 id="script">Scriptdef</h2>
<h3>Description</h3>
<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>
+<a href="http://jakarta.apache.org/bsf" target="_top">Apache BSF</a>
or
<a href="https://scripting.dev.java.net">JSR 223</a>
may be
@@ -66,13 +66,13 @@ to use "someattribute" to retrieve the attribute's value from the
<p>The name "self" (<i>since Ant 1.6.3</i>) is a pre-defined reference to the
script def task instance.
It can be used for logging, or for integration with the rest of
- ant. the <code>self.text attribute</code> contains
+ Ant. the <code>self.text attribute</code> contains
any nested text passed to the script</p>
-<p>If an attribute or element is not passed in,
-then <code>attributes.get()</code> or <code>elements.get()</code> will
-return null. It is up to the script to perform any checks and validation.
-<code>self.fail(String message)</code>can be used to raise a
+<p>If an attribute or element is not passed in,
+then <code>attributes.get()</code> or <code>elements.get()</code> will
+return null. It is up to the script to perform any checks and validation.
+<code>self.fail(String message)</code>can be used to raise a
<code>BuildException</code>.
</p>
@@ -84,7 +84,7 @@ more information on writing scripts, please refer to the
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -125,7 +125,7 @@ more information on writing scripts, please refer to the
<td valign="top">If true, the script is compiled before the first
evaluation for faster multiple executions, on the condition that the <em>manager</em> is "javax" and the
target engine implements <code>javax.script.Compilable</code>.
- Note that the <code>bsf</code> manager may automatically compiles the script.
+ Note that the <code>bsf</code> manager may automatically compiles the script.
<em>since Ant 1.10.2.</em></td>
<td valign="top" align="center">No - defaults to false</td>
</tr>
@@ -152,7 +152,7 @@ more information on writing scripts, please refer to the
<tr>
<td valign="top">loaderRef</td>
<td valign="top">the name of the loader that is
- used to load the script, constructed from the specified
+ used to load the script, constructed from the specified
classpath. This allows multiple script definitions
to reuse the same class loader.
</td>
@@ -162,7 +162,7 @@ more information on writing scripts, please refer to the
<h3>Nested elements</h3>
<h4>attribute</h4>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -176,7 +176,7 @@ more information on writing scripts, please refer to the
</table>
<h4>element</h4>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -206,8 +206,8 @@ more information on writing scripts, please refer to the
</tr>
<tr>
<td valign="top">any resource or resource collection</td>
- <td valign="top">Since Ant1.7.1, this task can load scripts
- from any resource supplied as a nested element. when </td>
+ <td valign="top"><em>Since Ant 1.7.1</em>, this task can load scripts
+ from any resource supplied as a nested element.</td>
<td valign="top" align="center">No</td>
</tr>
@@ -289,10 +289,10 @@ statement (scriptdef <code><scripttest2></code>; line 10)</code></p>
Script errors are only detected when a script task is actually executed.
</p>
<p>
- The next example does uses nested text in Jython. It also declares
- the script in a new xml namespace, which must be used to refer to
- the task. Declaring scripts in a new namespace guarantees that Ant will
- not create a task of the same (namespace,localname) name pair.
+ The next example does uses nested text in Jython. It also declares
+ the script in a new xml namespace, which must be used to refer to
+ the task. Declaring scripts in a new namespace guarantees that Ant will
+ not create a task of the same (namespace,localname) name pair.
</p>
<pre>
@@ -335,12 +335,9 @@ The next example shows the use of <classpath> and
<h3>Testing Scripts</h3>
<p>
-The easiest way to test scripts is to use the
+The easiest way to test scripts is to use the
<a href="http://ant.apache.org/antlibs/antunit/">AntUnit</a> ant library.
-This will run all targets in a script that begin with "test" (and their dependencies). </p>
-
-
-
+This will run all targets in a script that begin with "test" (and their dependencies).</p>
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sequential.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sequential.html b/manual/Tasks/sequential.html
index d3deda6..3551d60 100644
--- a/manual/Tasks/sequential.html
+++ b/manual/Tasks/sequential.html
@@ -26,13 +26,13 @@
<h2>Sequential</h2>
<h3>Description</h3>
-<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
+<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>
-<p>The sequential task has no attributes and does not support any nested
-elements apart from Ant tasks. Any valid Ant task may be embedded within the
+<p>The sequential task has no attributes and does not support any nested
+elements apart from Ant tasks. Any valid Ant task may be embedded within the
sequential task.</p>
<h3>Example</h3>
@@ -47,9 +47,7 @@ sequential task.</p>
</parallel>
</pre>
<p>This example shows how the sequential task is used to execute three tasks in
-sequence, while another task is being executed in a separate thread. </p>
-
+sequence, while another task is being executed in a separate thread.</p>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/serverdeploy.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/serverdeploy.html b/manual/Tasks/serverdeploy.html
index 87d0777..bfe738e 100644
--- a/manual/Tasks/serverdeploy.html
+++ b/manual/Tasks/serverdeploy.html
@@ -25,7 +25,7 @@
<body>
-<h1><a name="serverdeploy">Apache Ant ServerDeploy User Manual</a></h1>
+<h1 id="serverdeploy">Apache Ant ServerDeploy User Manual</h1>
<p>by</p>
<!-- Names are in alphabetical order, on last name -->
<ul>
@@ -33,21 +33,21 @@
<li>Cyrille Morvan (<a href="mailto:cmorvan@ingenosya.com">cmorvan@ingenosya.com</a>)</li>
</ul>
-</p>
-<hr>
-<p> At present the tasks support:<br>
+<hr/>
+<p>At present the tasks support:</p>
<ul>
<li><a href="http://www.bea.com" target="_top">Weblogic</a> servers</li>
<li><a href="http://www.objectweb.org/jonas/" target="_top">JOnAS</a>
2.4 Open Source EJB server</li>
</ul>
+<p>
Over time we expect further optional tasks to support additional J2EE Servers.
</p>
-<hr>
+<hr/>
-<table border="1" cellpadding="5">
+<table>
<tr><td>Task</td><td colspan="2">Application Servers</td></tr>
<tr><td rowspan="4"><a href="#serverdeploy_element">serverdeploy</a></td><td colspan="2" align="center"><b>Nested Elements</b></td></tr>
<tr><td><a href="#serverdeploy_generic">generic</a></td><td>Generic task</td></tr>
@@ -56,8 +56,7 @@ Over time we expect further optional tasks to support additional J2EE Servers.
</table>
-<a name="serverdeploy_element">
-<h2>ServerDeploy element</h2>
+<h2 id="serverdeploy_element">ServerDeploy element</h2>
<h3><b>Description:</b></h3>
@@ -69,7 +68,7 @@ attributes are required, depending on the tool.
</p>
<h3>Parameters:</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -98,7 +97,7 @@ attributes are required, depending on the tool.
<h3>Vendor-specific nested elements</h3>
<h3>Parameters used for all tools:</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -129,8 +128,7 @@ attributes are required, depending on the tool.
<p>Also supported are nested vendor-specific elements.</p>
-<a name="serverdeploy_generic">
-<h3>Generic element</h3>
+<h3 id="serverdeploy_generic">Generic element</h3>
This element is provided for generic Java-based deployment tools.
The generic task accepts (but does not require) nested <code>arg</code>
and <code>jvmarg</code> elements.
@@ -138,8 +136,7 @@ A JVM will be spawned with the provided attributes. It is recommended
that a vendor-specific element be used over the generic one if at all
possible.
<p>The following attributes are supported by the generic element.</p>
-<p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -152,7 +149,6 @@ possible.
<td>Yes</td>
</tr>
</table>
-</p>
<h3>Nested Elements</h3>
<p>The generic element supports nested <code><arg></code> and <code><jvmarg></code> elements.</p>
@@ -176,8 +172,7 @@ using a Java based deploy tool:</p>
</serverdeploy>
</pre>
-<a name="serverdeploy_weblogic">
-<h3>WebLogic element</h3>
+<h3 id="serverdeploy_weblogic">WebLogic element</h3>
<p>
The WebLogic element contains additional attributes to run the
<code>weblogic.deploy</code> deployment tool.
@@ -190,7 +185,7 @@ the <code>application</code> attribute must be set. If the <code>username</code
attribute is omitted, it defaults to "system". The <code>password</code> attribute is
required for all actions.
<p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -247,17 +242,16 @@ WebLogic server:</p>
</serverdeploy>
</pre>
-<a name="serverdeploy_jonas">
-<h3>JOnAS (Java Open Application Server) element</h3>
+<h3 id="serverdeploy_jonas">JOnAS (Java Open Application Server) element</h3>
<p>
The JOnAS element contains additional attributes to run the
<code>JonasAdmin</code> deployment tool.
<p>Valid actions for the tool are <code>deploy</code>, <code>undeploy</code>,
<code>list</code> and <code>update</code>.
-<p>You can't use <code>user</code> and <code>password</code> property with this
+<p>You can't use <code>user</code> and <code>password</code> property with this
task.
<p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -272,7 +266,7 @@ task.
<td valign="top">orb</td>
<td valign="top">Choose your ORB : RMI, JEREMIE, DAVID, ... If omitted, it defaults
to the one present in classpath. The corresponding JOnAS JAR is
- automatically added to the classpath. If your orb is DAVID (RMI/IIOP) you must
+ automatically added to the classpath. If your orb is DAVID (RMI/IIOP) you must
specify davidhost and davidport properties.</td>
<td>No</td>
</tr>
@@ -329,7 +323,5 @@ JOnAS server and a WebLogic server:</p>
</serverdeploy>
</pre>
-
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/setpermissions.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/setpermissions.html b/manual/Tasks/setpermissions.html
index 22a6fb8..427c545 100644
--- a/manual/Tasks/setpermissions.html
+++ b/manual/Tasks/setpermissions.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="setpermissions">SetPermissions</a></h2>
+<h2 id="setpermissions">SetPermissions</h2>
<p><em>Since Ant 1.10.0.</em></p>
<h3>Description</h3>
<p>Changes the file permissions using Java's NIO support for
@@ -35,7 +35,7 @@
<p>If no permissions are specified either via the mode or the
permissions attribute, then all permissions will be removed from the
nested resources.</p>
-<p>The task accepts aribitrary resources as part of the nested
+<p>The task accepts arbitrary resources as part of the nested
resource collections, but not all resources support setting
permissions. This task won't do anything for resources that don't
support setting permissions - for example URLs.</p>
@@ -45,7 +45,7 @@
permissions to apply to either type of resource.</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -61,7 +61,7 @@
</tr>
<tr>
<td valign="top">mode</td>
- <td valign="top">The permissions to set as tradional Unix
+ <td valign="top">The permissions to set as traditional Unix
three-digit octal number.</td>
<td valign="top" align="center">No</td>
</tr>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/setproxy.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/setproxy.html b/manual/Tasks/setproxy.html
index b6da936..a191dda 100644
--- a/manual/Tasks/setproxy.html
+++ b/manual/Tasks/setproxy.html
@@ -36,7 +36,7 @@ Sets Java's web proxy properties, so that tasks and code run in the same JVM can
<pre><setproxy socksproxyhost="socksy"/></pre> use socks via socksy:1080
<pre><setproxy socksproxyhost=""/></pre> stop using the socks server.
<p>
-You can set a username and password for http with the <tt>proxyHost</tt> and <tt>proxyPassword</tt> attributes. On Java1.4 and above these can also be used against SOCKS5 servers.
+You can set a username and password for http with the <tt>proxyHost</tt> and <tt>proxyPassword</tt> attributes. On Java 1.4 and above these can also be used against SOCKS5 servers.
</p>
<h3 id="attributes">Parameters</h3>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/signjar.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/signjar.html b/manual/Tasks/signjar.html
index 0ff24df..c17f94e 100644
--- a/manual/Tasks/signjar.html
+++ b/manual/Tasks/signjar.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="signjar">SignJar</a></h2>
+<h2 id="signjar">SignJar</h2>
<h3>Description</h3>
<p>Signing a jar allows users to authenticate the publisher.</p>
<p>Signs JAR files with the <a target="_blank" href="http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jarsigner.html"><tt>jarsigner</tt> command line tool</a>.
@@ -47,7 +47,7 @@ and <tt>lazy</tt> is false, the JAR is signed.</li>
</ul>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -138,13 +138,13 @@ block</td>
<tr>
<td valign="top">tsaurl</td>
<td valign="top">URL for a timestamp authority for timestamped
- JAR files in Java1.5+</td>
+ JAR files in Java 5+</td>
<td valign="top" align="center">No</td>
</tr>
<tr>
<td valign="top">tsacert</td>
<td valign="top">alias in the keystore for a timestamp authority for
- timestamped JAR files in Java1.5+</td>
+ timestamped JAR files in Java 5+</td>
<td valign="top" align="center">No</td>
</tr>
<tr>
@@ -191,7 +191,7 @@ block</td>
</tr>
</table>
<h3>Parameters as nested elements</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -204,7 +204,7 @@ block</td>
</tr>
<tr>
<td valign="top">fileset</td>
- <td valign="top">fileset of JAR files to sign. </td>
+ <td valign="top">fileset of JAR files to sign.</td>
<td valign="top" align="center">No</td>
</tr>
<tr>
@@ -215,7 +215,7 @@ block</td>
<tr>
<td valign="top">sysproperty</td>
<td valign="top">JVM system properties, with the syntax of Ant
- <a href="exec.html#env">environment variables</a> </td>
+ <a href="exec.html#env">environment variables</a></td>
<td valign="top" align="center">No, and only one can be supplied</td>
</tr>
</table>
@@ -287,18 +287,17 @@ SHA256withRSA.
With trusted timestamping, users can verify that signing occurred before a certificate's expiration or revocation. Without this timestamp, users can only verify the signature as of their current date.</p>
<p>
-Timestamped JAR files were introduced in Java1.5 and supported in Ant since
+Timestamped JAR files were introduced in Java 5 and supported in Ant since
Ant 1.7. Since Ant 1.9.5, Ant can use unauthenticated proxies for this signing process.
</p>
-<p>Common public timestamp authorities include
+<p>Common public timestamp authorities include</p>
<ul>
<li>http://timestamp.verisign.com</li>
<li>http://tsa.starfieldtech.com</li>
<li>https://timestamp.geotrust.com/tsa</li>
<li>Others (see your certificate authority)</li>
- </ul></p>
+ </ul>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sleep.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sleep.html b/manual/Tasks/sleep.html
index 80827b5..d6e4d10 100644
--- a/manual/Tasks/sleep.html
+++ b/manual/Tasks/sleep.html
@@ -23,63 +23,63 @@
<body>
-<h2><a name="sleep">Sleep</a></h2>
+<h2 id="sleep">Sleep</h2>
<h3>Description</h3>
-<p> A task for sleeping a short period of time, useful when a build or deployment
- process requires an interval between tasks.</p>
+<p>
+A task for sleeping a short period of time, useful when a build or deployment
+process requires an interval between tasks.
+</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
- <tr>
+<table>
+ <tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
<td align="center" valign="top"><b>Required</b></td>
</tr>
- <tr>
+ <tr>
<td valign="top">hours</td>
<td valign="top">hours to to add to the sleep time</td>
<td valign="top" align="center">No</td>
</tr>
- <tr>
+ <tr>
<td valign="top">minutes</td>
<td valign="top"> minutes to add to the sleep time</td>
<td valign="top" align="center">No</td>
</tr>
- <tr>
+ <tr>
<td valign="top">seconds</td>
<td valign="top">seconds to add to the sleep time</td>
<td align="center" valign="top">No</td>
</tr>
- <tr>
+ <tr>
<td valign="top">milliseconds</td>
<td valign="top">milliseconds to add to the sleep time</td>
<td align="center" valign="top">No</td>
</tr>
- <tr>
+ <tr>
<td valign="top">failonerror</td>
- <td valign="top">flag controlling whether to break the build on an error.
+ <td valign="top">flag controlling whether to break the build on an error.
</td>
<td align="center" valign="top">No</td>
</tr>
</table>
-<p>The sleep time is the sum of specified values, hours, minutes seconds and milliseconds.
- A negative value can be supplied to any of them provided the total sleep time
+<p>The sleep time is the sum of specified values, hours, minutes seconds and milliseconds.
+ A negative value can be supplied to any of them provided the total sleep time
is positive</p>
-<p>Note that sleep times are always hints to be interpred by the OS how it feels
- - small times may either be ignored or rounded up to a minimum timeslice. Note
- also that the system clocks often have a fairly low granularity too, which complicates
+<p>Note that sleep times are always hints to be interpreted by the OS how it feels
+ - small times may either be ignored or rounded up to a minimum timeslice. Note
+ also that the system clocks often have a fairly low granularity too, which complicates
measuring how long a sleep actually took.</p>
<h3>Examples</h3>
<pre> <sleep milliseconds="10"/></pre>
-Sleep for about 10 mS.
+Sleep for about 10 mS.
<pre> <sleep seconds="2"/></pre>
-Sleep for about 2 seconds.
+Sleep for about 2 seconds.
<pre> <sleep hours="1" minutes="-59" seconds="-58"/></pre>
-<p>Sleep for one hour less 59:58, or two seconds again </p>
+<p>Sleep for one hour less 59:58, or two seconds again</p>
<pre> <sleep/></pre>
-Sleep for no time at all. This may yield the CPU time to another thread or process.
-
+Sleep for no time at all. This may yield the CPU time to another thread or process.
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sos.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sos.html b/manual/Tasks/sos.html
index c068263..9908290 100644
--- a/manual/Tasks/sos.html
+++ b/manual/Tasks/sos.html
@@ -14,14 +14,10 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
-
- <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<link rel="stylesheet" type="text/css" href="../stylesheets/style.css">
-<title>SOS Tasks</title>
-
+ <title>SOS Tasks</title>
</head>
<body>
@@ -32,21 +28,19 @@
<ul>
<li><a href="mailto:jesse@cryptocard.com">Jesse Stockall</a></li>
</ul>
+<p>
Version 1.1 2002/01/23
-<br>
-<br>
-
-<hr width="100%" size="2">
+</p>
+<hr/>
<h2>Contents</h2>
<ul>
<li><a href="#intro">Introduction</a></li>
<li><a href="#tasks">The Tasks</a></li>
-
</ul>
<br>
-<h2><a name="intro">Introduction</a> </h2>
+<h2 id="intro">Introduction</h2>
<p>These tasks provide an interface to the <a href="http://msdn.microsoft.com/ssafe/default.asp" target="_top">
Microsoft Visual SourceSafe</a> SCM via <a href="http://www.sourcegear.com">
@@ -63,9 +57,9 @@ 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
have been tested with Linux, Solaris & Windows2000.</p>
-<h2><a name="tasks">The Tasks</a> </h2>
+<h2 id="tasks">The Tasks</h2>
-<table border="0" cellspacing="0" cellpadding="3">
+<table>
<tbody>
<tr>
<td><a href="#SOSGet">sosget</a></td>
@@ -88,20 +82,17 @@ have been tested with Linux, Solaris & Windows2000.</p>
</tbody>
</table>
- <br>
-
-<hr width="100%" size="2">
+<hr/>
<h2>Task Descriptions</h2>
-<h2><a name="SOSGet"></a>SOSGet<br>
- </h2>
+<h2 id="SOSGet">SOSGet</h2>
<h3>Description</h3>
Task to perform GET commands with SOS<br>
<h3>Parameters</h3>
</div>
</div>
-<table border="1">
+<table>
<tbody>
<tr>
<th>Attribute</th>
@@ -200,22 +191,23 @@ have been tested with Linux, Solaris & Windows2000.</p>
sosserverpath="192.168.10.6:8888"
vssserverpath="d:\vss\srcsafe.ini"/>
</pre>
+<p>
<small>Connects to a SourceOffsite server on 192.168.10.6:8888 with
build,build as the username & password. The SourceSafe database resides
on the same box as the SOS server & the VSS database is at
"d:\vss\srcsafe.ini" Does a recursive GetProject on
$/SourceRoot/project1, using tmp as the working
-directory. </small><br>
-<br>
+directory. </small>
+</p>
-<hr width="100%" size="2">
-<h2><a name="SOSLabel"></a>SOSLabel</h2>
+<hr/>
+<h2 id="SOSLabel">SOSLabel</h2>
<h3>Description</h3>
Task to perform Label commands with SOS<br>
<h3>Parameters</h3>
-<table border="1">
+<table>
<tbody><tr>
<th>Attribute</th>
<th>Values</th>
@@ -279,22 +271,21 @@ directory. </small><br>
sosserverpath="192.168.10.6:8888"
vssserverpath="d:\vss\srcsafe.ini"/>
</pre>
-
+<p>
<small>Connects to a SourceOffsite server on 192.168.10.6:8888 with
build,build as the username & password. The SourceSafe database resides
on the same box as the SOS server & the VSS database is at
"d:\vss\srcsafe.ini". Labels the $/SourceRoot/project1
-project with "test label".</small><br>
-<br>
-
-<hr width="100%" size="2"><br>
+project with "test label".</small>
+</p>
-<h2><a name="SOSCheckIn"></a>SOSCheckIn</h2>
+<hr/>
+<h2 id="SOSCheckIn">SOSCheckIn</h2>
<h3>Description</h3>
Task to perform CheckIn commands with SOS<br>
<h3>Parameters</h3>
-<table border="1">
+<table>
<tbody>
<tr>
<th>Attribute</th>
@@ -386,23 +377,24 @@ project with "test label".</small><br>
vssserverpath="\\server2\vss\srcsafe.ini"/>
</pre>
+<p>
<small>Connects to a SourceOffsite server on server1:8888 with build,build as
the username & password. The SourceSafe database resides on a different
box (server2) & the VSS database is on a share called
"vss". Checks-in only the "foobar.txt" file adding
a comment of "comment abc". Extra status messages will be
-displayed on screen.</small><br>
-<br>
+displayed on screen.</small>
+</p>
-<hr width="100%" size="2">
-<h2><a name="SOSCheckOut"></a>SOSCheckOut</h2>
+<hr/>
+<h2 id="SOSCheckOut">SOSCheckOut</h2>
<h3>Description</h3>
Task to perform CheckOut commands with SOS<br>
<h3>Parameters</h3>
-<table border="1">
+<table>
<tbody>
<tr>
<th>Attribute</th>
@@ -489,15 +481,15 @@ displayed on screen.</small><br>
sosserverpath="192.168.10.6:8888"
vssserverpath="\\server2\vss\srcsafe.ini"/>
</pre>
-
+<p>
<small>Connects to a SourceOffsite server on server1:8888 with build,build as
the username & password. The SourceSafe database resides on a different
box (server2) & the VSS database is on a share called
"vss". Checks-out "project1", Only the
"project1" directory will be locked as the recursive option
was not set. Extra status messages will be displayed on screen. The
-soscmd(.exe) file to be used resides in /usr/local/bin.</small><br>
-<br>
+soscmd(.exe) file to be used resides in /usr/local/bin.</small>
+</p>
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sound.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sound.html b/manual/Tasks/sound.html
index 1095f80..96821f7 100644
--- a/manual/Tasks/sound.html
+++ b/manual/Tasks/sound.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="sound">Sound</a></h2>
+<h2 id="sound">Sound</h2>
<h3>Description</h3>
<p>Plays a sound-file at the end of the build, according to whether
the build failed or succeeded. You can specify either a specific
@@ -32,14 +32,14 @@ sound-file to play, or, if a directory is specified, the
<code><sound></code> task will randomly select a file to play.
Note: At this point, the random selection is based on all the files
in the directory, not just those ending in appropriate suffixes
-for sound-files, so be sure you only have sound-files in the
+for sound-files, so be sure you only have sound-files in the
directory you specify.</p>
<p>More precisely <code><sound></code> registers a hook that is
triggered when the build finishes. Therefore you have to place this
task as top level or inside a target which is always executed.</p>
<p>
Unless you are running on Java 1.3 or later, you need the Java Media Framework
-on the classpath (javax.sound).
+on the classpath (javax.sound).
</p>
@@ -51,9 +51,9 @@ on the classpath (javax.sound).
<h3>Nested Element Parameters</h3>
<p>
-The following attributes may be used on the <code><success></code>
+The following attributes may be used on the <code><success></code>
and <code><fail></code> elements:</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -116,8 +116,5 @@ more than once.
</blockquote>
randomly selects a sound-file to play when the build succeeds or fails.
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/splash.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/splash.html b/manual/Tasks/splash.html
index e158bd2..cf8bcad 100644
--- a/manual/Tasks/splash.html
+++ b/manual/Tasks/splash.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="Splash">Splash</a></h2>
+<h2 id="splash">Splash</h2>
<p>by Les Hughes (leslie.hughes@rubus.com)
<h3>Description</h3>
<p>This task creates a splash screen. The splash screen is displayed
@@ -32,7 +32,7 @@ for the duration of the build and includes a handy progress bar as
well. Use in conjunction with the sound task to provide interest
whilst waiting for your builds to complete...</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -45,7 +45,7 @@ whilst waiting for your builds to complete...</p>
<td valign="top" align="center">No</td>
<td valign="top" align="center">antlogo.gif from the classpath</td>
</tr>
-
+
<tr>
<td valign="top">showduration</td>
<td valign="top">Initial period to pause the build to show the
@@ -76,11 +76,11 @@ whilst waiting for your builds to complete...</p>
The following properties can be used to configure the proxy settings to retrieve
an image from behind a firewall. However, the settings apply not just to this
-task, but to all following tasks. Therefore they are now deprecated in
+task, but to all following tasks. Therefore they are now deprecated in
preference to the <code><setproxy></code> task, that makes it clear to readers of
the build exactly what is going on.
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top">useproxy</td>
<td valign="top">Use a proxy to access imgurl. Note: Only tested
@@ -147,8 +147,5 @@ the build exactly what is going on.
</target>
</pre></blockquote>
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sql.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sql.html b/manual/Tasks/sql.html
index bade590..d7873ae 100644
--- a/manual/Tasks/sql.html
+++ b/manual/Tasks/sql.html
@@ -22,39 +22,39 @@
</head>
<body>
-<h2><a name="sql">Sql</a></h2>
+<h2 id="sql">Sql</h2>
<h3>Description</h3>
-<p>Executes a series of SQL statements via JDBC to a database. Statements can
-either be read in from a text file using the <i>src</i> attribute or from
+<p>Executes a series of SQL statements via JDBC to a database. Statements can
+either be read in from a text file using the <i>src</i> attribute or from
between the enclosing SQL tags.</p>
-<p>Multiple statements can be provided, separated by semicolons (or the
-defined <i>delimiter</i>). Individual lines within the statements can be
+<p>Multiple statements can be provided, separated by semicolons (or the
+defined <i>delimiter</i>). Individual lines within the statements can be
commented using either --, // or REM at the start of the line.</p>
-<p>The <i>autocommit</i> attribute specifies whether auto-commit should be
-turned on or off whilst executing the statements. If auto-commit is turned
-on each statement will be executed and committed. If it is turned off the
+<p>The <i>autocommit</i> attribute specifies whether auto-commit should be
+turned on or off whilst executing the statements. If auto-commit is turned
+on each statement will be executed and committed. If it is turned off the
statements will all be executed as one transaction.</p>
-<p>The <i>onerror</i> attribute specifies how to proceed when an error occurs
-during the execution of one of the statements.
+<p>The <i>onerror</i> attribute specifies how to proceed when an error occurs
+during the execution of one of the statements.
The possible values are: <b>continue</b> execution, only show the error;
<b>stop</b> execution, log the error but don't fail the task
and <b>abort</b> execution and transaction and fail task.</p>
<p>
-<b>Proxies</b>. Some JDBC drivers (including the Oracle thin driver),
+<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 Apache Ant1.7, Ant running on Java1.5 or later defaults to
+ Since Apache Ant 1.7, Ant running on Java 5 or later defaults to
<a href="../proxy.html">using
- the proxy settings of the operating system</a>.
+ the proxy settings of the operating system</a>.
Accordingly, the OS proxy settings need to be valid, or Ant's proxy
support disabled with <code>-noproxy</code> option.
</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
<td width="78%" valign="top"><b>Description</b></td>
@@ -93,7 +93,7 @@ and <b>abort</b> execution and transaction and fail task.</p>
<tr>
<td valign="top">outputencoding</td>
<td valign="top">The encoding of the files holding
- results. <em>since 1.9.4</em</td>
+ results. <em>since 1.9.4</em></td>
<td align="center">No - defaults to default JVM encoding</td>
</tr>
<tr>
@@ -292,12 +292,12 @@ and <b>abort</b> execution and transaction and fail task.</p>
<h3>Parameters specified as nested elements</h3>
<h4>transaction</h4>
-<p>Use nested <code><transaction></code>
+<p>Use nested <code><transaction></code>
elements to specify multiple blocks of commands to the executed
executed in the same connection but different transactions. This
is particularly useful when there are multiple files to execute
on the same schema.</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -333,7 +333,7 @@ href="../using.html#path">PATH like structure</a> and can also be set via a nest
<p>Use nested <code><connectionProperty></code> elements to
specify additional JDBC properties that need to be set when
connecting to the database.</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -357,12 +357,11 @@ href="../using.html#path">PATH like structure</a> and can also be set via a nest
url="jdbc:database-url"
userid="sa"
password="pass"
- src="data.sql"
-/>
+ src="data.sql"/>
</pre></blockquote>
-<p>Connects to the database given in <i>url</i> as the sa user using the
-org.database.jdbcDriver and executes the SQL statements contained within
+<p>Connects to the database given in <i>url</i> as the sa user using the
+org.database.jdbcDriver and executes the SQL statements contained within
the file data.sql</p>
<blockquote><pre><sql
@@ -384,8 +383,7 @@ property <i>internal_logon</i> to the value <i>SYSDBA</i>.</p>
driver="org.database.jdbcDriver"
url="jdbc:database-url"
userid="sa"
- password="pass"
- >
+ password="pass">
insert
into table some_table
values(1,2,3,4);
@@ -395,7 +393,7 @@ truncate table some_other_table;
</pre></blockquote>
<p>Connects to the database given in <i>url</i> as the sa
- user using the org.database.jdbcDriver and executes the two SQL statements
+ user using the org.database.jdbcDriver and executes the two SQL statements
inserting data into some_table and truncating some_other_table. Ant Properties
in the nested text will not be expanded.</p>
@@ -408,8 +406,7 @@ or other special characters. For example:</p>
driver="org.database.jdbcDriver"
url="jdbc:database-url"
userid="sa"
- password="pass"
- ><![CDATA[
+ password="pass"><![CDATA[
update some_table set column1 = column1 + 1 where column2 < 42;
@@ -417,32 +414,30 @@ update some_table set column1 = column1 + 1 where column2 < 42;
</pre></blockquote>
The following command turns property expansion in nested text on (it is off purely for backwards
-compatibility), then creates a new user in the HSQLDB database using Ant properties.
+compatibility), then creates a new user in the HSQLDB database using Ant properties.
<blockquote><pre><sql
driver="org.hsqldb.jdbcDriver";
url="jdbc:hsqldb:file:${database.dir}"
userid="sa"
password=""
- expandProperties="true"
- >
+ expandProperties="true">
<transaction>
CREATE USER ${newuser} PASSWORD ${newpassword}
</transaction>
</sql>
</pre></blockquote>
-
-<p>The following connects to the database given in url as the sa user using
-the org.database.jdbcDriver and executes the SQL statements contained within
-the files data1.sql, data2.sql and data3.sql and then executes the truncate
+<p>The following connects to the database given in url as the sa user using
+the org.database.jdbcDriver and executes the SQL statements contained within
+the files data1.sql, data2.sql and data3.sql and then executes the truncate
operation on <i>some_other_table</i>.</p>
<blockquote><pre><sql
driver="org.database.jdbcDriver"
url="jdbc:database-url"
userid="sa"
- password="pass" >
+ password="pass">
<transaction src="data1.sql"/>
<transaction src="data2.sql"/>
<transaction src="data3.sql"/>
@@ -473,9 +468,9 @@ run before <code>data2.sql</code>.</p>
</sql>
</pre></blockquote>
-<p>The following connects to the database given in url as the sa user using the
-org.database.jdbcDriver and executes the SQL statements contained within the
-file data.sql, with output piped to outputfile.txt, searching /some/jdbc.jar
+<p>The following connects to the database given in url as the sa user using the
+org.database.jdbcDriver and executes the SQL statements contained within the
+file data.sql, with output piped to outputfile.txt, searching /some/jdbc.jar
as well as the system classpath for the driver class.</p>
<blockquote><pre><sql
@@ -485,15 +480,14 @@ as well as the system classpath for the driver class.</p>
password="pass"
src="data.sql"
print="yes"
- output="outputfile.txt"
- >
+ output="outputfile.txt">
<classpath>
<pathelement location="/some/jdbc.jar"/>
</classpath>
</sql>
</pre></blockquote>
-<p>The following will only execute if the RDBMS is "oracle" and the version
+<p>The following will only execute if the RDBMS is "oracle" and the version
starts with "8.1."</p>
<blockquote><pre><sql
@@ -503,8 +497,7 @@ starts with "8.1."</p>
password="pass"
src="data.sql"
rdbms="oracle"
- version="8.1."
- >
+ version="8.1.">
insert
into table some_table
values(1,2,3,4);
@@ -513,6 +506,5 @@ truncate table some_other_table;
</sql>
</pre></blockquote>
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sshexec.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sshexec.html b/manual/Tasks/sshexec.html
index d085abd..5efa5bd 100644
--- a/manual/Tasks/sshexec.html
+++ b/manual/Tasks/sshexec.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="sshexec">SSHEXEC</a></h2>
+<h2 id="sshexec">SSHEXEC</h2>
<h3>Description</h3>
<p><em>since Apache Ant 1.6</em></p>
@@ -42,7 +42,7 @@ and won't work with versions of jsch earlier than
<p>See also the <a href="scp.html">scp task</a></p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -61,18 +61,18 @@ and won't work with versions of jsch earlier than
<tr>
<td valign="top">command</td>
<td valign="top">The command to run on the remote host.</td>
- <td valian="top" align="center">Either this or commandResource must be set</td>
+ <td valign="top" align="center">Either this or commandResource must be set</td>
</tr>
<tr>
<td valign="top">commandResource</td>
<td valign="top">The resource (file) that contains the commands to run on the remote host.
Since Ant 1.7.1</td>
- <td valian="top" align="center">Either this or command must be set</td>
+ <td valign="top" align="center">Either this or command must be set</td>
</tr>
<tr>
<td valign="top">port</td>
<td valign="top">The port to connect to on the remote host.</td>
- <td valian="top" align="center">No, defaults to 22.</td>
+ <td valign="top" align="center">No, defaults to 22.</td>
</tr>
<tr>
<td valign="top">trust</td>
@@ -81,14 +81,14 @@ and won't work with versions of jsch earlier than
<strong>Note</strong> If you set this to false (the default), the
host you connect to must be listed in your knownhosts file, this
also implies that the file exists.</td>
- <td valian="top" align="center">No, defaults to No.</td>
+ <td valign="top" align="center">No, defaults to No.</td>
</tr>
<tr>
<td valign="top">knownhosts</td>
<td valign="top">This sets the known hosts file to use to validate
the identity of the remote host. This must be a SSH2 format file.
SSH1 format is not supported.</td>
- <td valian="top" align="center">No, defaults to
+ <td valign="top" align="center">No, defaults to
${user.home}/.ssh/known_hosts.</td>
</tr>
<tr>
@@ -152,7 +152,7 @@ and won't work with versions of jsch earlier than
</tr>
<tr>
<td valign="top">outputproperty</td>
- <td valign="top">The name of a property in which the output of the
+ <td valign="top">The name of a property in which the output of the
command should be stored. If you use the commandResource
attribute, each command's output will be prefixed by the
command itself.</td>
@@ -191,8 +191,8 @@ and won't work with versions of jsch earlier than
</tr>
<tr>
<td valign="top">verbose</td>
- <td valign="top">Determines whether sshexec outputs verbosely to the user.<br/>
- Similar output is generated as the ssh commandline tool wit the -v option.
+ <td valign="top">Determines whether sshexec outputs verbosely to the user.<br/>
+ Similar output is generated as the ssh commandline tool wit the -v option.
<em>since Ant 1.8.0</em></td>
<td align="center">No, defaults to false</td>
</tr>
@@ -283,21 +283,20 @@ and won't work with versions of jsch earlier than
commandResource="to_run"/>
</pre>
-
<p><strong>Security Note:</strong> Hard coding passwords and/or usernames
in sshexec task can be a serious security hole. Consider using variable
-substitution and include the password on the command line. For example:<br>
+substitution and include the password on the command line. For example:</p>
<pre>
<sshexec host="somehost"
username="${username}"
password="${password}"
command="touch somefile"/>
</pre>
-Invoking ant with the following command line:
+Invoking Ant with the following command line:
<pre>
ant -Dusername=me -Dpassword=mypassword target1 target2
</pre>
-
+<p>
Is slightly better, but the username/password is exposed to all users
on an Unix system (via the ps command). The best approach is to use
the
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sshsession.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sshsession.html b/manual/Tasks/sshsession.html
index e9696d1..4758719 100644
--- a/manual/Tasks/sshsession.html
+++ b/manual/Tasks/sshsession.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="sshsession">SSHSESSION</a></h2>
+<h2 id="sshsession">SSHSESSION</h2>
<h3>Description</h3>
<p><em>since Apache Ant 1.8.0</em></p>
@@ -46,7 +46,7 @@ than 0.1.28.</p>
and <a href="scp.html">scp</a> tasks</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -65,7 +65,7 @@ and <a href="scp.html">scp</a> tasks</p>
<tr>
<td valign="top">port</td>
<td valign="top">The port to connect to on the remote host.</td>
- <td valian="top" align="center">No, defaults to 22.</td>
+ <td valign="top" align="center">No, defaults to 22.</td>
</tr>
<tr>
<tr>
@@ -75,7 +75,7 @@ and <a href="scp.html">scp</a> tasks</p>
local port forwarding.<br> If
nested <a href="#LocalTunnel">localtunnel</a> elements are also
provided, both sets of tunnels will be established.</td>
- <td valian="top" align="center">No</td>
+ <td valign="top" align="center">No</td>
</tr>
<tr>
<td valign="top">remotetunnels</td>
@@ -84,23 +84,23 @@ and <a href="scp.html">scp</a> tasks</p>
remote port forwarding.<br> If
nested <a href="#RemoteTunnel">remotetunnel</a> elements are
also provided, both sets of tunnels will be established.</td>
- <td valian="top" align="center">No</td>
+ <td valign="top" align="center">No</td>
</tr>
<tr>
<td valign="top">trust</td>
-
+
<td valign="top">This trusts all unknown hosts if set to yes/true.<br>
<strong>Note</strong> If you set this to false (the default), the
host you connect to must be listed in your knownhosts file, this
also implies that the file exists.</td>
- <td valian="top" align="center">No, defaults to No.</td>
+ <td valign="top" align="center">No, defaults to No.</td>
</tr>
<tr>
<td valign="top">knownhosts</td>
<td valign="top">This sets the known hosts file to use to validate
the identity of the remote host. This must be a SSH2 format file.
SSH1 format is not supported.</td>
- <td valian="top" align="center">No, defaults to
+ <td valign="top" align="center">No, defaults to
${user.home}/.ssh/known_hosts.</td>
</tr>
<tr>
@@ -138,13 +138,13 @@ and <a href="scp.html">scp</a> tasks</p>
<h3>Parameters specified as nested elements</h3>
-<a name="LocalTunnel"><h4>localtunnel</h4></a>
+<h4 id="LocalTunnel">localtunnel</h4>
<p>Optionally, any number of localtunnel elements can be used to
define local port forwarding over the SSH connection. If the
localtunnels parameter was also specified, both sets of tunnels will
be established.</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -169,13 +169,13 @@ be established.</p>
</tr>
</table>
-<a name="RemoteTunnel"><h4>remotetunnel</h4></a>
+<h4 id="RemoteTunnel">remotetunnel</h4>
<p>Optionally, any number of remotetunnel elements can be used to
define remote port forwarding over the SSH connection. If the
remotetunnels parameter was also specified, both sets of tunnels will
be established.</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -200,7 +200,7 @@ be established.</p>
</tr>
</table>
-<a name="Sequential"><h4>sequential</h4></a>
+<h4 id="Sequential">sequential</h4>
<p>The sequential element is a required parameter. It is a container
for nested Tasks which are to be executed once the SSH connection is
established and all local and/or remote tunnels established.</p>
@@ -213,14 +213,12 @@ command locally, which can use the tunnel.</b></p>
<sshsession host="somehost"
username="dude"
password="yo"
- localtunnels="2401:localhost:2401"
- >
+ localtunnels="2401:localhost:2401">
<sequential>
- <cvs command="update ${cvs.parms} ${module}"
+ <cvs command="update ${cvs.parms} ${module}"
cvsRoot="${cvs.root}"
dest="${local.root}"
- failonerror="true"
- />
+ failonerror="true"/>
</sequential>
</sshsession>
</pre>
@@ -229,15 +227,13 @@ command locally, which can use the tunnel.</b></p>
<pre>
<sshsession host="somehost"
username="dude"
- password="yo"
- >
+ password="yo">
<localtunnel lport="2401" rhost="localhost" rport="2401"/>
<sequential>
- <cvs command="update ${cvs.parms} ${module}"
+ <cvs command="update ${cvs.parms} ${module}"
cvsRoot="${cvs.root}"
dest="${local.root}"
- failonerror="true"
- />
+ failonerror="true"/>
</sequential>
</sshsession>
</pre>
@@ -261,7 +257,7 @@ accessible, then run a get task using that tunnel.</b></p>
<p><strong>Security Note:</strong> Hard coding passwords or
passphrases and/or usernames in sshsession task can be a serious
security hole. Consider using variable substitution and include the
-password on the command line. For example:<br>
+password on the command line. For example:</p>
<pre>
<sshsession host="somehost"
username="${username}"
@@ -273,11 +269,11 @@ password on the command line. For example:<br>
</sshsession>
</pre>
-Invoking ant with the following command line:
+Invoking Ant with the following command line:
<pre>
ant -Dusername=me -Dpassword=mypassword target1 target2
</pre>
-
+<p>
Is slightly better, but the username/password is exposed to all users
on an Unix system (via the ps command). The best approach is to use
the
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/style.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/style.html b/manual/Tasks/style.html
index 81e7e6b..496e621 100644
--- a/manual/Tasks/style.html
+++ b/manual/Tasks/style.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="style">XSLT</a></h2>
+<h2 id="style">XSLT</h2>
<p><em>The name <code>style</code> is a deprecated name for the same task.</em></p>
<h3>Description</h3>
<p>Process a set of documents via XSLT.</p>
@@ -86,7 +86,7 @@ element which is used to perform Entity and URI resolution.</p>
classloader (reference to an Ant PATH-like structure).</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -117,11 +117,11 @@ element which is used to perform Entity and URI resolution.</p>
<td valign="top">name of the stylesheet to use - given either relative
to the project's basedir or as an absolute path.<br/>
<br/>
- Alternatively, a nested element which ant can interpret as a resource
+ Alternatively, a nested element which Ant can interpret as a resource
can be used to indicate where to find the stylesheet<br/>
<em>deprecated variation :</em> <br/>
If the stylesheet cannot be found, and if you have specified the
- attribute basedir for the task, ant will assume that the style
+ attribute basedir for the task, Ant will assume that the style
attribute is relative to the basedir of the task.
</td>
<td align="center" valign="top">No, if the location of
@@ -147,14 +147,13 @@ element which is used to perform Entity and URI resolution.</p>
</tr>
<tr>
<td valign="top">processor</td>
-
<td valign="top">name of the XSLT processor to use.
Permissible value is :<ul>
<li>"trax" for a TraX compliant processor (ie JAXP interface
implementation such as Xalan 2 or Saxon)</li></ul>
Defaults to trax.
<br/>
- Support for xalan1 has been removed in ant 1.7.
+ Support for Xalan 1 has been removed in Ant 1.7.
</td>
<td align="center" valign="top">No</td>
</tr>
@@ -237,7 +236,7 @@ element which is used to perform Entity and URI resolution.</p>
<td valign="top">Specifies a xsl parameter for accessing the directory
of the current processed file. For files in the current directory a
value of '.' will be passed to the transformation.
- If not set, the directory is not passed to the transformation.
+ If not set, the directory is not passed to the transformation.
<em>Since Ant 1.7</em>.</td>
<td valign="top" align="center">No</td>
</tr>
@@ -245,7 +244,7 @@ element which is used to perform Entity and URI resolution.</p>
<td valign="top">suppressWarnings</td>
<td valign="top">Whether processor warnings shall be suppressed.
This option requires support by the processor, it is supported by
- the trax processor bundled with Ant.
+ the trax processor bundled with Ant.
<em>Since Ant 1.8.0</em>.</td>
<td valign="top" align="center">No, default is false.</td>
</tr>
@@ -286,7 +285,7 @@ collection</a></h4>
should be applied to. Use a nested mapper and the task's destdir
attribute to specify the output files.</p>
-<h4><a name="classpath">classpath</a></h4>
+<h4 id="classpath">classpath</h4>
<p>The classpath to load the processor from can be specified via a
nested <code><classpath></code>, as well - that is, a
<a href="../using.html#path">path</a>-like structure.</p>
@@ -299,7 +298,7 @@ element is used to perform Entity and URI resolution.</p>
<p>Param is used to pass a parameter to the XSL stylesheet.</p>
<blockquote>
<h4>Parameters</h4>
-<table width="60%" border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -352,7 +351,7 @@ element is used to perform Entity and URI resolution.</p>
</table>
</blockquote>
- <p>
+ <p>
The <code>XPATH_*</code> types says that the <code>expression</code> is not just a primitive-type value but an XPath expression.
This expression will be evaluated on an empty XML document and the result will be passed to the XSLT transformer as a parameter of given type.
In these expressions the declared Ant properties can be used as XPath variables e.g. <code>$someProperty</code>.
@@ -370,7 +369,7 @@ as specified in the <a href="http://www.w3.org/TR/xslt#output">
XSLT specifications</a>.
<blockquote>
<h4>Parameters</h4>
-<table width="60%" border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -389,11 +388,11 @@ XSLT specifications</a>.
</table>
</blockquote>
-<h4><a name="factory">factory ('trax' processors only)</a></h4>
+<h4 id="factory">factory ('trax' processors only)</h4>
Used to specify factory settings.
<blockquote>
<h4>Parameters</h4>
-<table width="60%" border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -433,7 +432,7 @@ And in Saxon 7.x:
</ul>
<blockquote>
<h4>Parameters</h4>
-<table width="60%" border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -491,7 +490,7 @@ support
is <code>http://javax.xml.XMLConstants/feature/secure-processing</code>.
<blockquote>
<h4>Parameters</h4>
-<table width="60%" border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -580,9 +579,9 @@ with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>
element <xsl:param name="date"/>, the variable
<code>$date</code> will subsequently have the value 07-01-2000.
</p>
-
+
<p>Various data types and XPath expressions:</p>
-
+
<pre><property name="antProperty1" value="ANT_PROPERTY_1"/>
<property name="antProperty2" value="ANT_PROPERTY_2"/>
<property name="antProperty3" value="3"/>
@@ -594,38 +593,38 @@ with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>
-->
<xslt in="in.xml" out="out.xml" style="template.xsl">
-
+
<!-- Simple String parameter: -->
<param name="p0" expression="some nice string" type="STRING"/>
-
+
<!-- A value substituted by Ant -->
<param name="p1" expression="some string with ${antProperty1} constructed by Ant" type="STRING"/>
-
+
<!-- XPath resulting in: and this is done in XPath: ANT_PROPERTY_2 -->
<param name="p2" expression="concat('and this is done in XPath: ', $antProperty2)" type="XPATH_STRING"/>
-
+
<!-- Some XPath math, result: 42 -->
<param name="p3" expression="64 * 64 div 128 + 10" type="XPATH_NUMBER"/>
-
+
<!-- Some numeric parameter: -->
<param name="p4" expression="123.45" type="DOUBLE"/>
-
+
<!-- XPath expression, result: true boolean -->
<param name="p5" expression="$antProperty1 = 'ANT_PROPERTY_1'" type="XPATH_BOOLEAN"/>
-
+
<!-- First one is an XPath variable, second one is a text substituted by Ant, result: true boolean -->
<param name="p6" expression="$antProperty2 = '${antProperty2}'" type="XPATH_BOOLEAN"/>
-
+
<!-- Some XPath math with a variable, result: 64 -->
<param name="p7" expression="$antProperty3 * 4 * 5 + 4" type="XPATH_NUMBER"/>
-
- <!--
+
+ <!--
XPath expression with substituted function name and a variable:
substring-before($antProperty2, '_')
result: ANT
-->
<param name="p8" expression="${antProperty4}($antProperty2, '_')" type="XPATH_STRING"/>
-
+
<!-- Without type attribute: -->
<param name="p9" expression="default type is String"/>
</xslt></pre>
@@ -700,6 +699,5 @@ with <a href="../Types/propertyset.html">syspropertyset</a>s.</p>
</pre>
</blockquote>
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/subant.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/subant.html b/manual/Tasks/subant.html
index 8cc4c29..c5bc952 100644
--- a/manual/Tasks/subant.html
+++ b/manual/Tasks/subant.html
@@ -28,7 +28,7 @@
<p>
Calls a given target for all defined sub-builds.
This is an extension
- of ant for bulk project execution.
+ 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
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/symlink.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/symlink.html b/manual/Tasks/symlink.html
index 6c98f5e..2ed74fc 100644
--- a/manual/Tasks/symlink.html
+++ b/manual/Tasks/symlink.html
@@ -24,17 +24,20 @@
<body>
-<h2><a name="symlink">Symlink</a></h2>
+<h2 id="symlink">Symlink</h2>
<h3>Description</h3>
-<p> Manages symbolic links on platforms where Java supports symbolic links.
+<p>
+Manages symbolic links on platforms where Java supports symbolic links.
Can be used to make an individual link, delete a link, create multiple links
from properties files, or create properties files describing links in the
specified directories. Existing files are not overwritten by default.
-
-<p><a href="../Types/fileset.html">FileSet</a>s are used to select a
-set of links to record, or a set of property files to create links from. </p>
+</p>
+<p>
+<a href="../Types/fileset.html">FileSet</a>s are used to select a
+set of links to record, or a set of property files to create links from.
+</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -72,7 +75,7 @@ set of links to record, or a set of property files to create links from. </p>
</tr>
<tr>
<td valign="top">overwrite</td>
- <td valign="top">Overwrite existing files or not. If overwrite is set to true, then
+ <td valign="top">Overwrite existing files or not. If overwrite is set to true, then
any existing file, specified by the link attribute, will be overwritten irrespective
of whether or not the existing file is a symbolic link.</td>
<td valign="top" align="center">No; defaults to false.</td>
@@ -96,12 +99,12 @@ set of links to record, or a set of property files to create links from. </p>
<h3>Examples</h3>
- <p> Make a link named "foo" to a resource named "bar.foo" in subdir:</p>
+ <p>Make a link named "foo" to a resource named "bar.foo" in subdir:</p>
<pre>
<symlink link="${dir.top}/foo" resource="${dir.top}/subdir/bar.foo"/>
</pre>
- <p> Record all links in subdir and it's descendants in files named
+ <p>Record all links in subdir and it's descendants in files named
"dir.links"</p>
<pre>
<symlink action="record" linkfilename="dir.links">
@@ -109,14 +112,14 @@ set of links to record, or a set of property files to create links from. </p>
</symlink>
</pre>
- <p> Recreate the links recorded in the previous example:</p>
+ <p>Recreate the links recorded in the previous example:</p>
<pre>
<symlink action="recreate">
<fileset dir="${dir.top}" includes="subdir/**/dir.links"/>
</symlink>
</pre>
- <p> Delete a link named "foo":
+ <p>Delete a link named "foo":</p>
<pre>
<symlink action="delete" link="${dir.top}/foo"/>
</pre>
@@ -127,12 +130,10 @@ set of links to record, or a set of property files to create links from. </p>
IOException where Apache Ant can't find /some/working/directory${ANT_HOME}/bin/antRun
or something similar. The workaround is to change your ANT_HOME environment
variable to an absolute path, which will remove the /some/working/directory portion
- of the above path and allow ant to find the correct commandline execution script.
+ of the above path and allow Ant to find the correct commandline execution script.
<p><strong>NOTE:</strong> Starting Ant version 1.10.2, this task relies on the symbolic
link support introduced in Java 7 through the java.nio.file.Files APIs</p>
-
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/sync.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/sync.html b/manual/Tasks/sync.html
index 1d34aee..b1d4d1d 100644
--- a/manual/Tasks/sync.html
+++ b/manual/Tasks/sync.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="get">Sync</a></h2>
+<h2 id="get">Sync</h2>
<p><em>Since Apache Ant 1.6</em></p>
<h3>Description</h3>
@@ -37,7 +37,7 @@ file in your sources and a file of that name is present in the target
dir, it will get removed from the target.</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -47,7 +47,7 @@ dir, it will get removed from the target.</p>
<td valign="top">todir</td>
<td valign="top">the target directory to sync with the resource collections</td>
<td align="center" valign="top">Yes</td>
- </tr>
+ </tr>
<tr>
<td valign="top">overwrite</td>
<td valign="top">Overwrite existing files even if the destination
@@ -116,7 +116,7 @@ support the dir attribute and the usedefaultexcludes attribute
defaults to false.</p>
<h5>Additional Parameters</h5>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -132,7 +132,7 @@ defaults to false.</p>
"wins".</td>
<td align="center" valign="top">No, defaults to the value of the
task's includeemptydirs attribute</td>
- </tr>
+ </tr>
</table>
<h3>Examples</h3>
@@ -159,8 +159,5 @@ present in <em>generated-site</em>.</p>
present in <em>generated-site</em> but keeps all files in any
<em>CVS</em> sub-directory.</p>
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/tar.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/tar.html b/manual/Tasks/tar.html
index 7d08c01..ae972e7 100644
--- a/manual/Tasks/tar.html
+++ b/manual/Tasks/tar.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="tar">Tar</a></h2>
+<h2 id="tar">Tar</h2>
<h3>Description</h3>
<p>Creates a tar archive.</p>
<p>The <i>basedir</i> attribute is the reference directory from where to tar.</p>
@@ -78,14 +78,14 @@ that it produces a warning for each file path encountered that does not match
the limit. It uses gnu rather than posix for backwards compatibility
reasons.</p>
-<p>To achivieve best interoperability you should use
+<p>To achieve best interoperability you should use
either <code>fail</code> or <code>posix</code> for the longfile attribute.</p>
<p>This task can perform compression by setting the compression attribute to "gzip"
or "bzip2".</p>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -141,7 +141,7 @@ or "bzip2".</p>
</tr>
<tr>
<td valign="top">compression</td>
- <td valign="top">compression method. Allowable values are
+ <td valign="top">compression method. Allowable values are
"none", "gzip", "xz" and "bzip2". Default is
"none".</td>
<td valign="top" align="center">No</td>
@@ -165,7 +165,7 @@ extended <a href="../Types/fileset.html">FileSets</a> which,
in addition to the standard elements, support one additional
attributes
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td valign="top"><b>Attribute</b></td>
<td valign="top"><b>Description</b></td>
@@ -196,8 +196,7 @@ it.</p>
<pre>
<tar destfile="${dist}/manual.tar"
basedir="htdocs/manual"
- excludes="mydocs/**, **/todo.html"
-/></pre>
+ excludes="mydocs/**, **/todo.html"/></pre>
<p>tars all files in the <code>htdocs/manual</code> directory into a file called <code>manual.tar</code>
in the <code>${dist}</code> directory. Files in the directory <code>mydocs</code>,
or files with the name <code>todo.html</code> are excluded.</p>
@@ -242,11 +241,9 @@ or files with the name <code>todo.html</code> are excluded.</p>
where some files need to be marked as executable (mode 755)
and the rest are use the default mode (read-write by owner). The first
fileset selects just the executable files. The second fileset must exclude
-the executable files and include all others. </p>
+the executable files and include all others.</p>
-
-
-<p><strong>Note: </strong> The tar task does not ensure that a file is only selected
+<p><strong>Note:</strong> The tar task does not ensure that a file is only selected
by one resource collection. If the same file is selected by more than one collection, it will be included in the
tar file twice, with the same path.</p>
@@ -269,7 +266,7 @@ will be retained in the resulting tar archive.</p>
<p><strong>Note:</strong>
- Please note the tar task creates a tar file, it does not append
+ Please note the tar task creates a tar file, it does not append
to an existing tar file. The existing tar file is replaced instead.
As with most tasks in Ant, the task only takes action if the output
file (the tar file in this case) is older than the input files, or
@@ -278,4 +275,3 @@ will be retained in the resulting tar archive.</p>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/taskdef.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/taskdef.html b/manual/Tasks/taskdef.html
index 4f6f5d2..a83def4 100644
--- a/manual/Tasks/taskdef.html
+++ b/manual/Tasks/taskdef.html
@@ -24,12 +24,12 @@
<body>
-<h2><a name="taskdef">Taskdef</a></h2>
+<h2 id="taskdef">Taskdef</h2>
<h3>Description</h3>
<p>Adds a task definition to the current project, such that this new task can be
used in the current project.</p>
<p>This task is a form of <a href="typedef.html">Typedef</a> with the
- attributes "adapter" and "adaptto" set to the values
+ attributes "adapter" and "adaptto" set to the values
"org.apache.tools.ant.TaskAdapter" and "org.apache.tools.ant.Task"
respectively. Anything said in the <a href="typedef.html">manual
page of typedef</a> applies to taskdef as well.</p>
@@ -38,7 +38,5 @@
<p>makes a task called <code>myjavadoc</code> available to Apache Ant. The class <code>com.mydomain.JavadocTask</code>
implements the task.</p>
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/a04350e0/manual/Tasks/telnet.html
----------------------------------------------------------------------
diff --git a/manual/Tasks/telnet.html b/manual/Tasks/telnet.html
index 0ac65b3..c658864 100644
--- a/manual/Tasks/telnet.html
+++ b/manual/Tasks/telnet.html
@@ -24,19 +24,19 @@
<body>
-<h2><a name="telnet">Telnet</a></h2>
+<h2 id="telnet">Telnet</h2>
<h3>Description</h3>
-Task to automate a remote telnet session. The task uses
+Task to automate a remote telnet session. The task uses
nested <tt><read></tt> to indicate strings to wait for, and
-<tt><write></tt> tags to specify text to send.
+<tt><write></tt> tags to specify text to send.
-<p>If you do specify a userid and password, the system will
+<p>If you do specify a userid and password, the system will
assume a common unix prompt to wait on. This behavior can be easily over-ridden.</p>
<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>
<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<th>Attribute</th>
<th>Values</th>
@@ -73,16 +73,16 @@ See <a href="../install.html#librarydependencies">Library Dependencies</a> for m
<td>No</td>
</tr>
</table>
-<h3><a name="nested">Nested Elements</a></h3>
+<h3 id="nested">Nested Elements</h3>
The commands to send to the server, and responses to wait for, are
-described as nested elements.
+described as nested elements.
<h4>read</h4>
<p>declare (as a text child of this element) a string to wait for.
The element supports the timeout attribute, which overrides any
timeout specified for the task as a whole. It also has a <tt>string</tt>
-attribute, which is an alternative to specifying the string as
+attribute, which is an alternative to specifying the string as
a text element.
</p>
<i>Always declare an opening and closing
@@ -93,7 +93,7 @@ the final command has completed.
<h4>write</h4>
<p>describes the text to send to the server. The <tt>echo</tt> boolean
-attribute controls whether the string is echoed to the local log;
+attribute controls whether the string is echoed to the local log;
this is "true" by default
</p>
<h3>Examples</h3>
@@ -122,8 +122,8 @@ This task can be rewritten as:
</telnet>
</pre></blockquote>
-A timeout can be specified at the <code><telnet></code> level or at the <code><read></code> level.
-This will connect, issue a sleep command that is suppressed from displaying and wait
+A timeout can be specified at the <code><telnet></code> level or at the <code><read></code> level.
+This will connect, issue a sleep command that is suppressed from displaying and wait
10 seconds before quitting.
<blockquote><pre>
<telnet userid="bob" password="badpass" server="localhost" timeout="20">
@@ -143,13 +143,11 @@ The task can be used with other ports as well:
</telnet>
</pre></blockquote>
<p>
-To use this task against the WinNT telnet service, you need to configure the service to use
-classic authentication rather than NTLM negotiated authentication.
-This can be done in the Telnet Server Admin app:
+To use this task against the WinNT telnet service, you need to configure the service to use
+classic authentication rather than NTLM negotiated authentication.
+This can be done in the Telnet Server Admin app:
select "display/change registry settings", then "NTLM", then set the value of NTLM to 1.
</p>
-
</body>
</html>
-