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/02/08 21:52:49 UTC
[3/3] ant git commit: Tidy tag soup, trim whitespace, fix styling
Tidy tag soup, trim whitespace, fix styling
Project: http://git-wip-us.apache.org/repos/asf/ant/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant/commit/5266b79b
Tree: http://git-wip-us.apache.org/repos/asf/ant/tree/5266b79b
Diff: http://git-wip-us.apache.org/repos/asf/ant/diff/5266b79b
Branch: refs/heads/master
Commit: 5266b79bb882f1912afa57abb1f19de6f03485e0
Parents: 94d36a9
Author: Gintas Grigelionis <gi...@apache.org>
Authored: Thu Feb 8 22:52:33 2018 +0100
Committer: Gintas Grigelionis <gi...@apache.org>
Committed: Thu Feb 8 22:52:33 2018 +0100
----------------------------------------------------------------------
manual/antexternal.html | 12 +-
manual/anttaskslist.html | 1 -
manual/argumentprocessor.html | 5 +-
manual/base_task_classes.html | 5 +-
manual/clonevm.html | 4 +-
manual/cover.html | 14 +-
manual/credits.html | 6 +-
manual/develop.html | 67 +--
manual/dirtasks.html | 27 +-
manual/feedback.html | 42 +-
manual/ide.html | 2 -
manual/ifunless.html | 8 +-
manual/inputhandler.html | 10 +-
manual/install.html | 55 +-
manual/installlist.html | 1 -
manual/intro.html | 7 +-
manual/javacprops.html | 6 +-
manual/listeners.html | 298 +++++-----
manual/platform.html | 98 ++--
manual/projecthelper.html | 15 +-
manual/properties.html | 22 +-
manual/proxy.html | 42 +-
manual/running.html | 89 ++-
manual/stylesheets/style.css | 57 ++
manual/sysclasspath.html | 4 +-
manual/targets.html | 20 +-
manual/tasksoverview.html | 610 ++++++++------------
manual/toc.html | 1 -
manual/tutorial-HelloWorldWithAnt.html | 92 ++-
manual/tutorial-tasks-filesets-properties.html | 138 ++---
manual/tutorial-writing-tasks.html | 71 +--
manual/tutorials.html | 8 +-
manual/using.html | 99 ++--
manual/usinglist.html | 1 -
34 files changed, 861 insertions(+), 1076 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/antexternal.html
----------------------------------------------------------------------
diff --git a/manual/antexternal.html b/manual/antexternal.html
index 02d2f7b..4f9bbc3 100644
--- a/manual/antexternal.html
+++ b/manual/antexternal.html
@@ -14,7 +14,6 @@
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-Language" content="en-us">
@@ -31,12 +30,12 @@
administrators. But what about programmers? Can the functionality
provided by Ant tasks be used in java programs?</p>
-<p>Yes, and its quite easy. Before getting into the details, however,
+<p>Yes, and its quite easy. Before getting into the details, however,
we should mention the pros and cons of this approach:
<h3>Pros</h3>
-<table cellpadding="0" margin="0" border="1">
+<table>
<tr>
<td><b>Robust</b></td>
<td>
@@ -65,7 +64,7 @@ code is supported by the entire Apache Ant community.
<h3>Cons</h3>
-<table cellpadding="0" margin="0" border="1">
+<table>
<tr>
<td><b>Dependency on Ant Libraries</b></td>
<td>
@@ -86,7 +85,6 @@ open source!
</tr>
</table>
-
<h2>Example</h2>
<p>Let's say you want to unzip a zip file programmatically from java
@@ -136,7 +134,7 @@ static public void unzip(String zipFilepath, String destinationDir) {
taskType = "unzip";
taskName = "unzip";
target = new Target();
- }
+ }
}
Expander expander = new Expander();
expander.setSrc(new File(zipfile));
@@ -156,5 +154,5 @@ don't. Ultimately, you have to be willing to get your feet wet and
read the source code. The above example is merely designed to whet
your appetite and get you started. Go for it!</p>
-
+</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/anttaskslist.html
----------------------------------------------------------------------
diff --git a/manual/anttaskslist.html b/manual/anttaskslist.html
index bd12049..b5b743b 100644
--- a/manual/anttaskslist.html
+++ b/manual/anttaskslist.html
@@ -25,7 +25,6 @@
<body>
-
<h2><a href="toc.html" target="navFrame">Table of Contents</a></h2>
<h3>Apache Ant Tasks</h3>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/argumentprocessor.html
----------------------------------------------------------------------
diff --git a/manual/argumentprocessor.html b/manual/argumentprocessor.html
index 2cd5202..ce7719e 100644
--- a/manual/argumentprocessor.html
+++ b/manual/argumentprocessor.html
@@ -25,7 +25,7 @@
<body>
<h1>The Command Line Processor Plugin: ArgumentProcessor</h1>
-<h2><a name="definition">What is an ArgumentProcessor?</a></h2>
+<h2 id="definition">What is an ArgumentProcessor?</h2>
<p>
An <code>ArgumentProcessor</code> is a parser of command line argument which is
@@ -59,7 +59,7 @@ being parsed and quit (like <code>-projectHelp</code>), or just set some
custom properties on the project and let it run.
</p>
-<h2><a name="repository">How to register it's own ArgumentProcessor</a></h2>
+<h2 id="repository">How to register it's own ArgumentProcessor</h2>
<p>First, the <code>ArgumentProcessor</code> must be an implementation of
<code>org.apache.tools.ant.ArgumentProcessor</code>.
@@ -73,4 +73,3 @@ be found in Ant's classpath.
</p>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/base_task_classes.html
----------------------------------------------------------------------
diff --git a/manual/base_task_classes.html b/manual/base_task_classes.html
index 1b058eb..801c26e 100644
--- a/manual/base_task_classes.html
+++ b/manual/base_task_classes.html
@@ -29,7 +29,7 @@
<p><strong>The links will not work in the online version of this document.</strong></p>
-<table border="1">
+<table>
<thead>
<tr>
<th>
@@ -86,7 +86,6 @@ Abstract Base class for pack tasks.
</td>
</tr>
-
<tr>
<td>
<a href="api/org/apache/tools/ant/taskdefs/Unpack.html">Unpack</a>
@@ -108,7 +107,5 @@ Abstract Base class for tasks that may have multiple actions.
</tbody>
</table>
-
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/clonevm.html
----------------------------------------------------------------------
diff --git a/manual/clonevm.html b/manual/clonevm.html
index b0a5342..e29ce6c 100644
--- a/manual/clonevm.html
+++ b/manual/clonevm.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="clonevm">ant.build.clonevm</a></h2>
+<h2 id="clonevm">ant.build.clonevm</h2>
<p><em>Since Apache Ant 1.7</em></p>
@@ -46,7 +46,5 @@ build.sysclasspath had the value "last".</p>
specified on the Ant command line. Use the ANT_OPTS environment
variable instead.</p>
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/cover.html
----------------------------------------------------------------------
diff --git a/manual/cover.html b/manual/cover.html
index 7075d60..2ef514c 100644
--- a/manual/cover.html
+++ b/manual/cover.html
@@ -22,19 +22,18 @@
<title>Apache Ant 1.10.3 User Manual</title>
</head>
-<body bgcolor="#FFFFFF">
-<div align="center">
+<body>
+<div align="center">
<h1><img src="images/ant_logo_large.gif" width="190" height="120"></h1>
<h1>Apache Ant™ 1.10.3 Manual</h1>
<p align="left">This is the manual for version 1.10.3 of
- <a target="_top" href="http://ant.apache.org/index.html">Apache Ant</a>.
- If your version
- of Ant (as verified with <tt>ant -version</tt>) is older or newer than this
- version then this is not the correct manual set. Please use the documentation
+ <a target="_top" href="http://ant.apache.org/index.html">Apache Ant</a>.
+ If your version
+ of Ant (as verified with <tt>ant -version</tt>) is older or newer than this
+ version then this is not the correct manual set. Please use the documentation
appropriate to your current version. Also, if you are using a version
older than the most recent release, we recommend an upgrade to fix bugs
as well as provide new functionality. </p>
- <p> </p>
<p align="left">Ant's manual and API documentation is part of
the <a href="http://ant.apache.org/bindownload.cgi">binary</a>
@@ -48,6 +47,5 @@
<p>Apache Ant, Apache Ivy, Ant, Ivy, Apache, the Apache feather logo, and the Apache Ant project logos are trademarks of The Apache Software Foundation.</p>
</div>
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/credits.html
----------------------------------------------------------------------
diff --git a/manual/credits.html b/manual/credits.html
index 1d9e4bf..275447d 100644
--- a/manual/credits.html
+++ b/manual/credits.html
@@ -18,7 +18,6 @@
<head>
<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title>Apache Ant User Manual - Credits</title>
</head>
@@ -44,9 +43,9 @@
<li>Bill Kelly (<a href="mailto:bill.kelly@softwired-inc.com">bill.kelly@softwired-inc.com</a>)</li>
<li>Martijn Kruithof</li>
<li>Arnout J. Kuiper (<a href="mailto:ajkuiper@wxs.nl">ajkuiper@wxs.nl</a>)</li>
- <li>Antoine L�vy-Lambert</li>
+ <li>Antoine Lévy-Lambert</li>
<li>Conor MacNeill</li>
- <li>Jan Mat�rne</li>
+ <li>Jan Matérne</li>
<li>Stefano Mazzocchi (<a href="mailto:stefano@apache.org">stefano@apache.org</a>)</li>
<li>Erik Meade (<a href="mailto:emeade@geekfarm.org">emeade@geekfarm.org</a>)</li>
<li>Sam Ruby (<a href="mailto:rubys@us.ibm.com">rubys@us.ibm.com</a>)</li>
@@ -65,6 +64,5 @@
<p>Version: 1.10.3</p>
</center>
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/develop.html
----------------------------------------------------------------------
diff --git a/manual/develop.html b/manual/develop.html
index 31add6a..65b711d 100644
--- a/manual/develop.html
+++ b/manual/develop.html
@@ -25,13 +25,13 @@
<body>
<h1>Developing with Apache Ant</h1>
-<h2><a name="writingowntask">Writing Your Own Task</a></h2>
+<h2 id="writingowntask">Writing Your Own Task</h2>
<p>It is very easy to write your own task:</p>
<ol>
<li>Create a Java class that extends <code>org.apache.tools.ant.Task</code>
or <a href="base_task_classes.html">another class</a> that was designed to be extended.</li>
- <li>For each attribute, write a <i>setter</i> method. The setter method must be a
+ <li id="footnote-1-back">For each attribute, write a <i>setter</i> method. The setter method must be a
<code>public void</code> method that takes a single argument. The
name of the method must begin with <code>set</code>, followed by the
attribute name, with the first character of the name in uppercase, and the rest in
@@ -44,7 +44,7 @@
<a href="Tasks/parallel.html"><code>parallel</code></a>), your
class must implement the interface
<code>org.apache.tools.ant.TaskContainer</code>. If you do so, your
- task can not support any other nested elements. See
+ task can not support any other nested elements. See
<a href="#taskcontainer">below</a>.</li>
<li>If the task should support character data (text nested between the
@@ -61,7 +61,7 @@
takes a single argument of an <code>Object</code> type with a
no-argument constructor. The name of the add (addConfigured) method
must begin with <code>add</code> (<code>addConfigured</code>),
- followed by the element name. For a more complete discussion see
+ followed by the element name. For a more complete discussion see
<a href="#nested-elements">below</a>.</li>
<li>Write a <code>public void execute</code> method, with no arguments, that
@@ -70,7 +70,7 @@
</ol>
<hr>
-<p><a name="footnote-1">*</a> Actually the case of the letters after
+<p id="footnote-1"><a href="#footnote-1-back">*</a> Actually the case of the letters after
the first one doesn't really matter to Ant, using all lower case is a
good convention, though.</p>
@@ -124,17 +124,17 @@ good convention, though.</p>
have been created for <code>addConfiguredXXX()</code> methods,
those methods get invoked now.</li>
- <li><a name="execute"><code>execute()</code></a> is called at runtime.
+ <li id="execute"><code>execute()</code> is called at runtime.
If <code>target1</code> and <code>target2</code> both depend
on <code>target3</code>, then running
<code>'ant target1 target2'</code> will run all tasks in
<code>target3</code> twice.</li>
</ol>
-<h3><a name="set-magic">Conversions Ant will perform for attributes</a></h3>
+<h3 id="set-magic">Conversions Ant will perform for attributes</h3>
<p>Ant will always expand properties before it passes the value of an
-attribute to the corresponding setter method. <b>Since Ant 1.8</b>, it is
+attribute to the corresponding setter method. <em>Since Ant 1.8</em>, it is
possible to <a href="Tasks/propertyhelper.html">extend Ant's property handling</a>
such that a non-string Object may be the result of the evaluation of a string
containing a single property reference. These will be assigned directly via
@@ -173,7 +173,7 @@ is more! If the argument of you setter method is</p>
<code>org.apache.tools.ant.types.Resource</code>, Ant will
resolve the string as a <code>java.io.File</code> as above, then
pass in as a <code>org.apache.tools.ant.types.resources.FileResource</code>.
- <b>Since Ant 1.8</b>
+ <em>Since Ant 1.8</em>
</li>
<li><code>org.apache.tools.ant.types.Path</code>, Ant will tokenize
@@ -205,7 +205,7 @@ is more! If the argument of you setter method is</p>
<code>toString()</code> in the enumeration is ignored; the build file must use
the declared name (see <code>Enum.getName()</code>). You may wish to use lowercase
enum constant names, in contrast to usual Java style, to look better in build files.
- <em>As of Ant 1.7.0.</em></li>
+ <em>Since Ant 1.7.0</em></li>
</ul>
@@ -216,7 +216,7 @@ setters Ant could chose from, only one of them will be called, but we
don't know which, this depends on the implementation of your Java
virtual machine.</p>
-<h3><a name="nested-elements">Supporting nested elements</a></h3>
+<h3 id="nested-elements">Supporting nested elements</h3>
<p>Let's assume your task shall support nested elements with the name
<code>inner</code>. First of all, you need a class that represents
@@ -261,7 +261,7 @@ handled.</p>
the methods will be called, but we don't know which, this depends on
the implementation of your Java virtual machine.</p>
-<h3><a name="nestedtype">Nested Types</a></h3>
+<h3 id="nestedtype">Nested Types</h3>
If your task needs to nest an arbitrary type that has been defined
using <code><typedef></code> you have two options.
<ol>
@@ -318,13 +318,13 @@ public class Sample {
interface MyInterface {
void setVerbose(boolean val);
- }
+ }
public static class BuildPath extends Path {
public BuildPath(Project project) {
super(project);
}
-
+
public void add(MyInterface inter) {}
public void setUrl(String url) {}
}
@@ -342,7 +342,6 @@ public class Sample {
as follows:
</p>
<pre>
- <blockquote>
<typedef name="myfileselector" classname="Sample$MyFileSelector"
classpath="classes" loaderref="classes"/>
<typedef name="buildpath" classname="Sample$BuildPath"
@@ -359,10 +358,9 @@ public class Sample {
</myfileselector>
</fileset>
</copy>
- </blockquote>
</pre>
-<h3><a name="taskcontainer">TaskContainer</a></h3>
+<h3 id="taskcontainer">TaskContainer</h3>
<p>The <code>TaskContainer</code> consists of a single method,
<code>addTask</code> that basically is the same as an <a
@@ -466,10 +464,8 @@ implementing class name to the <code>default.properties</code> file in the
<code>org.apache.tools.ant.taskdefs</code>
package. Then you can use it as if it were a built-in task.</p>
-
-
<hr>
-<h2><a name="buildevents">Build Events</a></h2>
+<h2 id="buildevents">Build Events</h2>
<p>Ant is capable of generating build events as it performs the tasks necessary to build a project.
Listeners can be attached to Ant to receive these events. This capability could be used, for example,
to connect Ant to a GUI or to integrate Ant with an IDE.
@@ -488,13 +484,13 @@ for the following events</p>
<li>Message logged</li>
</ul>
-<p>If the build file invokes another build file via
-<a href="Tasks/ant.html"><code><ant></code></a> or
-<a href="Tasks/subant.html"><code><subant></code></a> or uses
+<p>If the build file invokes another build file via
+<a href="Tasks/ant.html"><code><ant></code></a> or
+<a href="Tasks/subant.html"><code><subant></code></a> or uses
<a href="Tasks/antcall.html"><code><antcall></code></a>, you are creating a
new Ant "project" that will send target and task level events of its
-own but never sends build started/finished events. Ant 1.6.2
-introduces an extension of the BuildListener interface named
+ own but never sends build started/finished events. <em>Since Ant 1.6.2</em>,
+BuildListener interface has an extension named
SubBuildListener that will receive two new events for</p>
<ul>
<li>SubBuild started</li>
@@ -512,22 +508,18 @@ listener, of course).</p>
<p>will run Ant with a listener that generates an XML representation of the build progress. This
listener is included with Ant, as is the default listener, which generates the logging to standard output.</p>
-<p><b>Note: </b>A listener must not access System.out and System.err directly since output on
-these streams is redirected by Ant's core to the build event system. Accessing these
+<p><b>Note</b>: A listener must not access System.out and System.err directly since output on
+these streams is redirected by Ant's core to the build event system. Accessing these
streams can cause an infinite loop in Ant. Depending on the version of Ant, this will
-either cause the build to terminate or the Java VM to run out of Stack space. A logger, also, may
+either cause the build to terminate or the Java VM to run out of Stack space. A logger, also, may
not access System.out and System.err directly. It must use the streams with which it has
been configured.</p>
-<p><b>Note2:</b> All methods of a BuildListener except for the "Build
+<p><b>Note</b>: All methods of a BuildListener except for the "Build
Started" and "Build Finished" events may occur on several threads
simultaneously - for example while Ant is executing
a <code><parallel></code> task.</p>
-
-
-
-
<h3>Example</h3>
Writing an adapter to your favourite log library is very easy.
Just implent the BuildListener interface, instantiate your logger and delegate
@@ -565,25 +557,22 @@ public class MyLogAdapter implements BuildListener {
</pre>
</blockquote>
-
-
<hr>
-<h2><a name="integration">Source code integration</a></h2>
+<h2 id="integration">Source code integration</h2>
<p>The other way to extend Ant through Java is to make changes to existing tasks, which is positively encouraged.
Both changes to the existing source and new tasks can be incorporated back into the Ant codebase, which
benefits all users and spreads the maintenance load around.</p>
<p>Please consult the
-<a href="http://www.apache.org/foundation/getinvolved.html">Getting Involved</a> pages on the Apache web site
+<a href="https://www.apache.org/foundation/getinvolved.html">Getting Involved</a> pages on the Apache web site
for details on how to fetch the latest source and how to submit changes for reincorporation into the
source tree.</p>
<p>Ant also has some
-<a href="http://ant.apache.org/ant_task_guidelines.html">task guidelines</a>
+<a href="https://ant.apache.org/ant_task_guidelines.html">task guidelines</a>
which provides some advice to people developing and testing tasks. Even if you intend to
keep your tasks to yourself, you should still read this as it should be informative.</p>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/dirtasks.html
----------------------------------------------------------------------
diff --git a/manual/dirtasks.html b/manual/dirtasks.html
index 5c23229..a4c3347 100644
--- a/manual/dirtasks.html
+++ b/manual/dirtasks.html
@@ -24,7 +24,7 @@
<body>
-<h2><a name="directorybasedtasks">Directory-based Tasks</a></h2>
+<h2 id="directorybasedtasks">Directory-based Tasks</h2>
<p>Some tasks use directory trees for the actions they perform.
For example, the <a href="Tasks/javac.html">javac</a> task, which
compiles a directory tree with <code>.java</code> files into
@@ -45,7 +45,7 @@ which can be used at the same time:</p>
<li>Select files based on selection criteria defined by a collection of
<a href="Types/selectors.html">selector</a> nested elements.</li>
</ul>
-<h3><a name="patternset">Patternset</a></h3>
+<h3 id="patternset">Patternset</h3>
<p>We said that Directory-based tasks can sometimes act as an implicit
<a href="Types/fileset.html"><code><fileset></code></a>,
@@ -77,7 +77,7 @@ exclude patterns are used. If no include pattern is given, all files
are assumed to match the include pattern (with the possible exception of
the default excludes).</p>
-<h4><a name="patterns">Patterns</a></h4>
+<h4 id="patterns">Patterns</h4>
<p>As described earlier, patterns are used for the inclusion and exclusion
of files. These patterns look very much like the patterns used in DOS and
@@ -92,7 +92,7 @@ directory are considered. So while a pattern like
applied since the base directory's parent is never scanned for
files.</p>
-<p><b>Examples:</b></p>
+<h5>Examples:</h5>
<p>
<code>*.java</code> matches <code>.java</code>,
<code>x.java</code> and <code>FooBar.java</code>, but
@@ -129,8 +129,8 @@ or <code>\</code>, then <code>**</code>
is appended.
For example, <code>mypackage/test/</code> is interpreted as if it were
<code>mypackage/test/**</code>.</p>
-<p><b>Example patterns:</b></p>
-<table border="1" cellpadding="2" cellspacing="0">
+<h5>Example patterns:</h5>
+<table>
<tr>
<td valign="top"><code>**/CVS/*</code></td>
<td valign="top">Matches all files in <code>CVS</code>
@@ -189,7 +189,7 @@ For example, <code>mypackage/test/</code> is interpreted as if it were
<p>When these patterns are used in inclusion and exclusion, you have a powerful
way to select just the files you want.</p>
-<h3><a name="selectors">Selectors</a></h3>
+<h3 id="selectors">Selectors</h3>
<p>The <a href="Types/fileset.html"><code><fileset></code></a>,
whether implicit or explicit in the
directory-based task, also acts as an
@@ -199,7 +199,7 @@ selection criteria for the files the task should work with. See the
<a href="Types/selectors.html">Selector</a> documentation for more
information.</p>
-<h3><a name="tasklist">Standard Tasks/Filesets</a></h3>
+<h3 id="tasklist">Standard Tasks/Filesets</h3>
<p>Many of the standard tasks in ant take one or more filesets which follow
the rules given here. This list, a subset of those, is a list of standard ant
tasks that can act as an implicit fileset:</p>
@@ -232,7 +232,7 @@ tasks that can act as an implicit fileset:</p>
<li><a href="Tasks/wljspc.html"><code><wljspc></code></a></li>
</ul>
-<h3><a name="examples">Examples</a></h3>
+<h3 id="examples">Examples</h3>
<pre>
<copy todir="${dist}">
<fileset dir="${src}"
@@ -263,9 +263,9 @@ but excludes all <code>*.gif</code> files from the copy.</p>
<p>Deleting the original set of files, the <code>delete</code> task can act
as an implicit fileset.</p>
-<h3><a name="defaultexcludes">Default Excludes</a></h3>
+<h3 id="defaultexcludes">Default Excludes</h3>
<p>There are a set of definitions that are excluded by default from all
-directory-based tasks. As of Ant 1.8.1 they are:</p>
+ directory-based tasks. <em>Since Ant 1.8.1</em> they are:</p>
<pre>
**/*~
**/#*#
@@ -282,7 +282,7 @@ directory-based tasks. As of Ant 1.8.1 they are:</p>
**/.svn/**
**/.DS_Store
</pre>
-<p>Ant 1.8.2 adds the following default excludes:</p>
+<p><em>Since Ant 1.8.2</em>, additional default excludes are:</p>
<pre>
**/.git
**/.git/**
@@ -307,8 +307,5 @@ attribute.</p>
default excludes by using the <a
href="Tasks/defaultexcludes.html">defaultexcludes</a> task.</p>
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/feedback.html
----------------------------------------------------------------------
diff --git a/manual/feedback.html b/manual/feedback.html
index 70027f6..3baa19b 100644
--- a/manual/feedback.html
+++ b/manual/feedback.html
@@ -24,38 +24,38 @@
<body>
-<h1><a name="feedback">Feedback</a> and Troubleshooting</h1>
-<p>If things do not work, especially simple things like <tt>ant -version</tt>,
- then something is wrong with your configuration. Before filing bug reports and
+<h1 id="feedback">Feedback and Troubleshooting</h1>
+<p>If things do not work, especially simple things like <tt>ant -version</tt>,
+ then something is wrong with your configuration. Before filing bug reports and
emailing all the Apache Ant mailing lists</p>
<ol>
- <li>Check your environment variables. Are ANT_HOME and JAVA_HOME correct? If
+ <li>Check your environment variables. Are ANT_HOME and JAVA_HOME correct? If
they have quotes or trailing slashes, remove them.</li>
- <li>Unset CLASSPATH; if that is wrong things go horribly wrong. Ant does not
+ <li>Unset CLASSPATH; if that is wrong things go horribly wrong. Ant does not
need the CLASSPATH variable defined to anything to work.</li>
<li>Make sure there are no versions of crimson.jar or other XML parsers in JRE/ext</li>
- <li>Is your path correct? is Ant on it? What about JDK/bin? have you tested
- this? If you are using Jikes, is it on the path? A createProcess error (especially
+ <li>Is your path correct? is Ant on it? What about JDK/bin? have you tested
+ this? If you are using Jikes, is it on the path? A createProcess error (especially
with ID=2 on windows) usually means executable not found on the path.</li>
- <li>Which version of ant are you running? Other applications distribute a copy
+ <li>Which version of ant are you running? Other applications distribute a copy
-it may be being picked up by accident.</li>
- <li>If a task is failing to run is optional.jar in ANT_HOME/lib? Are there any
+ <li>If a task is failing to run is optional.jar in ANT_HOME/lib? Are there any
libraries which it depends on missing?</li>
- <li>If a task doesn't do what you expect, run <tt>ant -verbose</tt> or <tt>ant
+ <li>If a task doesn't do what you expect, run <tt>ant -verbose</tt> or <tt>ant
-debug</tt> to see what is happening</li>
</ol>
-<p>If you can't fix your problem, start with the <a href="http://ant.apache.org/mail.html" target="_top">Ant
- User Mailing List</a> . These are other ant users who will help you learn to
- use ant. If they cannot fix it then someone may suggest filing a bug report,
- which will escalate the issue. Remember of course, that support, like all open
- source development tasks, is voluntary. If you haven't invested time in helping
- yourself by following the steps above, it is unlikely that anyone will invest
+<p>If you can't fix your problem, start with the <a href="http://ant.apache.org/mail.html" target="_top">Ant
+ User Mailing List</a> . These are other ant users who will help you learn to
+ use ant. If they cannot fix it then someone may suggest filing a bug report,
+ which will escalate the issue. Remember of course, that support, like all open
+ source development tasks, is voluntary. If you haven't invested time in helping
+ yourself by following the steps above, it is unlikely that anyone will invest
the time in helping you. </p>
-<p>Also, if you don't understand something, the <a href="http://ant.apache.org/mail.html" target="_top">Ant
- User Mailing List</a> is the place to ask questions. Not the developer list,
- nor the individuals whose names appears in the source and documentation. If
+<p>Also, if you don't understand something, the <a href="http://ant.apache.org/mail.html" target="_top">Ant
+ User Mailing List</a> is the place to ask questions. Not the developer list,
+ nor the individuals whose names appears in the source and documentation. If
they answered all such emails, nobody would have any time to improve ant. </p>
-<p>To provide feedback on this software, please subscribe to the <a href="http://ant.apache.org/mail.html" target="_top">Ant
+<p>To provide feedback on this software, please subscribe to the <a href="http://ant.apache.org/mail.html" target="_top">Ant
User Mailing List</a> </p>
<p>If you want to contribute to Ant or stay current with the latest
@@ -66,7 +66,5 @@ development, join the
href="http://marc.theaimsgroup.com" target="_top">http://marc.theaimsgroup.com</a>.
Other archives will be documented online at <a href="http://ant.apache.org/mail.html#Archives" target="_top">Mailing Lists Archives</a> </p>
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/ide.html
----------------------------------------------------------------------
diff --git a/manual/ide.html b/manual/ide.html
index 7f2bc6d..e3d6bae 100644
--- a/manual/ide.html
+++ b/manual/ide.html
@@ -99,7 +99,5 @@ All the modern Java IDEs support Apache Ant almost out of the box.
</li>
</ul>
-
-
</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/ifunless.html
----------------------------------------------------------------------
diff --git a/manual/ifunless.html b/manual/ifunless.html
index abbdce1..8d0da2e 100644
--- a/manual/ifunless.html
+++ b/manual/ifunless.html
@@ -23,9 +23,9 @@
</head>
<body>
- <h1><a name="if_and_unless">If And Unless</a></h1>
+ <h1 id="if_and_unless">If And Unless</h1>
- <p>Since Ant 1.9.1 it is possible to add if and unless attributes on all tasks and nested elements using special namespaces.</p>
+ <p><em>Since Ant 1.9.1</em>, it is possible to add if and unless attributes on all tasks and nested elements using special namespaces.</p>
<p>In order to use this feature you need to add the following namespace declarations</p>
<blockquote><pre>
@@ -34,12 +34,12 @@
</pre>
</blockquote>
- <p>The if and unless namespaces support the following 3 conditions :
+ <p>The if and unless namespaces support the following 3 conditions:</p>
<ul>
<li>true</li>true if the value of the attribute evaluates to true
<li>blank</li>true if the value of the attribute is null or empty
<li>set</li>true if the specified property is set
- </ul></p>
+ </ul>
<blockquote>
<pre>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/inputhandler.html
----------------------------------------------------------------------
diff --git a/manual/inputhandler.html b/manual/inputhandler.html
index 1333157..67235df 100644
--- a/manual/inputhandler.html
+++ b/manual/inputhandler.html
@@ -49,7 +49,7 @@ every Ant process, users can specify the implementation using the
method</p>
<pre>
- void handleInput(InputRequest request)
+ void handleInput(InputRequest request)
throws org.apache.tools.ant.BuildException;
</pre>
@@ -60,7 +60,7 @@ situation.</p>
<p>Ant comes with three built-in implementations of this interface:</p>
-<h3><a name="defaulthandler">DefaultInputHandler</a></h3>
+<h3 id="defaulthandler">DefaultInputHandler</h3>
<p>This is the implementation you get, when you don't use the
<code>-inputhandler</code> command line switch at all. This
@@ -92,13 +92,13 @@ define it inside the <code>ANT_OPTS</code> environment variable.</p>
<p>Like the default implementation, this InputHandler reads from standard
input. However, it consumes <i>all</i> available input. This behavior is
-useful for sending Ant input via an OS pipe. <b>Since Ant 1.7</b>.</p>
+useful for sending Ant input via an OS pipe. <em>Since Ant 1.7</em></p>
<h3>SecureInputHandler</h3>
<p>This InputHandler calls <code>System.console().readPassword()</code>,
available since Java 1.6. On earlier platforms it falls back to the
-behavior of DefaultInputHandler. <b>Since Ant 1.7.1</b>.</p>
+behavior of DefaultInputHandler. <em>Since Ant 1.7.1</em></p>
<h2>InputRequest</h2>
@@ -112,5 +112,5 @@ input, but subclasses may use stricter validations.
should be used if the user input must be part of a predefined set of
choices.</p>
-
+</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/install.html
----------------------------------------------------------------------
diff --git a/manual/install.html b/manual/install.html
index 7a382d8..7051546 100644
--- a/manual/install.html
+++ b/manual/install.html
@@ -223,7 +223,7 @@ target="_top">http://archive.apache.org/dist/ant/</a>. The files are organized a
Ant has been used successfully on many platforms, including Linux, commercial flavours of Unix such as Solaris and
HP-UX, macOS, Windows NT descendants, OS/2 Warp, Novell Netware 6, OpenVMS. The platforms used most for development
are, in no particular order, Linux, macOS, Microsoft Windows and Unix; these are therefore that platforms that tend to
-work best. As of Ant 1.7, Windows 9x is no longer supported.
+ work best. <em>Since Ant 1.7</em>, Windows 9x is no longer supported.
</p>
<p>
For the current version of Ant (1.10), you will also need a JDK installed on your system, version 8 or later required.
@@ -275,36 +275,22 @@ To install Ant, choose a directory and copy the distribution files there. This d
<code>ANT_HOME</code>.
</p>
-<table width="80%">
-<tr>
- <td colspan="2">
- <b>Windows 95, Windows 98 & Windows ME Note:</b>
- </td>
-</tr>
-<tr>
- <td width="5%"> </td>
- <td>
+<h3>Windows 95, Windows 98 & Windows ME Note:</h3>
+ <p>
<i>Note that current releases of Ant no longer support these systems. If you are using an older version of Ant,
however, the script used to launch Ant will have problems if <code>ANT_HOME</code> is a long filename (i.e. a
filename which is not of the format known as "8.3"). This is due to limitations in the OS's handling of
the <code>"for"</code> batch file statement. It is recommended, therefore, that Ant be installed in a
<b>short</b>, 8.3 path, such as <code>C:\Ant</code>.</i>
- </td>
-</tr>
-<tr>
- <td width="5%"> </td>
- <td>
- <p>
+ </p>
+ <p>
On these systems you will also need to configure more environment space to cater for the environment variables used
in the Ant launch script. To do this, you will need to add or update the following line in the
<code>config.sys</code> file
- </p>
- <p>
+ </p>
+ <p>
<code>shell=c:\command.com c:\ /p /e:32768</code>
- </p>
- </td>
-</tr>
-</table>
+ </p>
<h3 id="setup">Setup</h3>
<p>
@@ -330,22 +316,13 @@ JDK/JRE. Ant is an application, whilst the extension directory is intended for J
security restrictions on the classes which may be loaded by an extension.
</p>
-<table width="80%">
-<tr>
- <td colspan="2">
- <b>Windows Note:</b>
- </td>
-</tr>
-<tr>
- <td width="5%"> </td>
- <td>
+<h3>Windows Note:</h3>
+<p>
The <code>ant.bat</code> script makes use of three environment variables - <code>ANT_HOME</code>,
<code>CLASSPATH</code> and <code>JAVA_HOME</code>. <b>Ensure</b> that <code>ANT_HOME</code> and
<code>JAVA_HOME</code> variables are set, and that they do <b><u>not</u></b> have quotes (either ' or ") and
they do <b><u>not</u></b> end with \ or with /. <code>CLASSPATH</code> should be unset or empty.
- </td>
-</tr>
-</table>
+</p>
<h3 id="checkInstallation">Check Installation</h3>
<p>
@@ -398,7 +375,7 @@ In <code><i>ANT_HOME</i>/lib</code>. This makes the JAR files available to all A
<li>
<p>
-In <code>${user.home}/.ant/lib</code> (as of Ant 1.6). This allows different users to add new libraries to Ant. All JAR
+ In <code>${user.home}/.ant/lib</code> (<em>since Ant 1.6</em>). This allows different users to add new libraries to Ant. All JAR
files added to this directory are available to command-line Ant.
</p>
</li>
@@ -418,7 +395,7 @@ applications, and causes no end of support calls. See <a href="#classpath">below
<li>
<p>
-In some <code><classpath></code> accepted by the task itself. For example, as of Ant 1.7.0 you can run
+ In some <code><classpath></code> accepted by the task itself. <em>Since Ant 1.7.0</em>, you can run
the <code><junit></code> task without <code>junit.jar</code> in Ant's own classpath, so long as it is included
(along with your program and tests) in the classpath passed when running the task.
</p>
@@ -627,7 +604,7 @@ version, it is not necessary to set <code> JAVA_HOME</code> or <code>ANT_HOME</c
installer will correctly place the Ant executable on your path.
</p>
<p>
-<b>NOTE:</b> <i>Since Ant 1.7.0</i>, if the <code>ANT_HOME</code> environment variable is set, the JPackage
+<b>Note</b>: <em>Since Ant 1.7.0</em>, if the <code>ANT_HOME</code> environment variable is set, the JPackage
distribution will be ignored.
</p>
<p>
@@ -716,7 +693,7 @@ on how to do this.
</p>
<p>
-As of version 1.7.0 Ant has a hard dependency on JUnit. The <code>fetch.xml</code> build script will download JUnit
+ <em>Since Ant 1.7.0</em>, Ant has a hard dependency on JUnit. The <code>fetch.xml</code> build script will download JUnit
automatically, but if you don't use this you must install it manually into <code>lib/optional</code> (download it
from <a href="http://junit.org/" target="_top">JUnit.org</a>) if you are using a source distribution of Ant.
</p>
@@ -797,7 +774,7 @@ automatically). You will also need to install the particular Ant optional JAR co
these tasks available. Please refer to the <a href="#optionalTasks"> Installing Ant / Optional Tasks</a> section above.
</p>
-<table border="1" cellpadding="2" cellspacing="0">
+<table>
<tr>
<td><b>JAR Name</b></td>
<td><b>Needed For</b></td>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/installlist.html
----------------------------------------------------------------------
diff --git a/manual/installlist.html b/manual/installlist.html
index 6bbe3dd..44f2ef4 100644
--- a/manual/installlist.html
+++ b/manual/installlist.html
@@ -41,4 +41,3 @@
</ul>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/intro.html
----------------------------------------------------------------------
diff --git a/manual/intro.html b/manual/intro.html
index e5673ed..1ffd3bf 100644
--- a/manual/intro.html
+++ b/manual/intro.html
@@ -23,7 +23,7 @@
</head>
<body>
-<h1><a name="introduction">Introduction</a></h1>
+<h1 id="introduction">Introduction</h1>
<p>Apache Ant is a Java-based build tool. In theory, it is kind of like
<i>make</i>, without <i>make</i>'s wrinkles.</p>
<h3>Why?</h3>
@@ -54,7 +54,7 @@ tasks get executed. Each task is run by an object that implements a particular
Task interface.</p>
<p>Granted, this removes some of the expressive power that is inherent in being
able to construct a shell command such as
-<nobr><code>`find . -name foo -exec rm {}`</code></nobr>, but it
+<code>`find . -name foo -exec rm {}`</code>, but it
gives you the ability to be cross-platform--to work anywhere and
everywhere. And
hey, if you really need to execute a shell command, Ant has an
@@ -62,8 +62,5 @@ hey, if you really need to execute a shell command, Ant has an
allows different commands to be executed based on the OS it is executing
on.</p>
-
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/javacprops.html
----------------------------------------------------------------------
diff --git a/manual/javacprops.html b/manual/javacprops.html
index 6cab07c..14430cc 100644
--- a/manual/javacprops.html
+++ b/manual/javacprops.html
@@ -33,21 +33,19 @@ change the build file, Apache Ant provides two properties that help you
setting default values for these attributes. If the attributes have
been set explicitly, the properties listed here will be ignored.</p>
-<h2><a name="source">ant.build.javac.source</a></h2>
+<h2 id="source">ant.build.javac.source</h2>
<p><em>Since Ant 1.7</em></p>
<p>Provides a default value for <code><javac></code>'s and
<code><javadoc></code>'s source attribute.</p>
-<h2><a name="target">ant.build.javac.target</a></h2>
+<h2 id="target">ant.build.javac.target</h2>
<p><em>Since Ant 1.7</em></p>
<p>Provides a default value for <code><javac></code>'s target
attribute.</p>
-
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/listeners.html
----------------------------------------------------------------------
diff --git a/manual/listeners.html b/manual/listeners.html
index 7387288..f21fe1a 100644
--- a/manual/listeners.html
+++ b/manual/listeners.html
@@ -25,12 +25,12 @@
<body>
<h1>Listeners & Loggers</h1>
-<h2><a name="Overview">Overview</a></h2>
+<h2 id="Overview">Overview</h2>
<p>Apache Ant has two related features to allow the build process to be monitored:
listeners and loggers.</p>
-<h3><a name="Listeners">Listeners</a></h3>
+<h3 id="Listeners">Listeners</h3>
<p>A listener is alerted of the following events:</p>
@@ -50,7 +50,7 @@ listeners and loggers.</p>
argument.
</p>
-<h3><a name="Loggers">Loggers</a></h3>
+<h3 id="Loggers">Loggers</h3>
<p>Loggers extend the capabilities of listeners and add the following features:</p>
@@ -61,228 +61,222 @@ listeners and loggers.</p>
<li>Emacs-mode aware</li>
</ul>
-<h2><a name="builtin">Built-in Listeners/Loggers</a></h2>
+<h2 id="builtin">Built-in Listeners/Loggers</h2>
-<table border="1" cellspacing="1" width="100%" id="AutoNumber1">
+<table>
<tr>
- <td width="33%">Classname</td>
- <td width="33%">Description</td>
- <td width="34%">Type</td>
+ <td>Classname</td>
+ <td>Description</td>
+ <td>Type</td>
</tr>
<tr>
- <td width="33%"><code><a href="#DefaultLogger">org.apache.tools.ant.DefaultLogger</a></code></td>
- <td width="33%">The logger used implicitly unless overridden with the
+ <td><code><a href="#DefaultLogger">org.apache.tools.ant.DefaultLogger</a></code></td>
+ <td>The logger used implicitly unless overridden with the
<code>-logger</code> command-line switch.</td>
- <td width="34%">BuildLogger</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#NoBannerLogger">
+ <td><code><a href="#NoBannerLogger">
org.apache.tools.ant.NoBannerLogger</a></code></td>
- <td width="33%">This logger omits output of empty target output.</td>
- <td width="34%">BuildLogger</td>
+ <td>This logger omits output of empty target output.</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#MailLogger">
+ <td><code><a href="#MailLogger">
org.apache.tools.ant.listener.MailLogger</a></code></td>
- <td width="33%">Extends DefaultLogger such that output is still generated
+ <td>Extends DefaultLogger such that output is still generated
the same, and when the build is finished an e-mail can be sent.</td>
- <td width="34%">BuildLogger</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#AnsiColorLogger">
+ <td><code><a href="#AnsiColorLogger">
org.apache.tools.ant.listener.AnsiColorLogger</a></code></td>
- <td width="33%">Colorifies the build output.</td>
- <td width="34%">BuildLogger</td>
+ <td>Colorifies the build output.</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#Log4jListener">
+ <td><code><a href="#Log4jListener">
org.apache.tools.ant.listener.Log4jListener</a></code></td>
- <td width="33%">
+ <td>
Passes events to Apache Log4j for highly customizable logging.<br>
<b>Deprecated:</b> Apache Log4j (1.x) is not developed any more. Last
release is 1.2.17 from 26-May-2012 and contains vulnerability issues.
</td>
- <td width="34%">BuildListener</td>
+ <td>BuildListener</td>
</tr>
<tr>
- <td width="33%"><code><a href="#XmlLogger">org.apache.tools.ant.XmlLogger</a></code></td>
- <td width="33%">Writes the build information to an XML file.</td>
- <td width="34%">BuildLogger</td>
+ <td><code><a href="#XmlLogger">org.apache.tools.ant.XmlLogger</a></code></td>
+ <td>Writes the build information to an XML file.</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#TimestampedLogger">org.apache.tools.ant.TimestampedLogger</a></code></td>
- <td width="33%">Prints the time that a build finished</td>
- <td width="34%">BuildLogger</td>
+ <td><code><a href="#TimestampedLogger">org.apache.tools.ant.TimestampedLogger</a></code></td>
+ <td>Prints the time that a build finished</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#BigProjectLogger">org.apache.tools.ant.listener.BigProjectLogger</a></code></td>
- <td width="33%">Prints the project name every target</td>
- <td width="34%">BuildLogger</td>
+ <td><code><a href="#BigProjectLogger">org.apache.tools.ant.listener.BigProjectLogger</a></code></td>
+ <td>Prints the project name every target</td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#SimpleBigProjectLogger">org.apache.tools.ant.listener.SimpleBigProjectLogger</a></code></td>
- <td width="33%">Prints the project name for subprojects only, otherwise like NoBannerLogger <em>Since Ant 1.8.1</em></td>
- <td width="34%">BuildLogger</td>
+ <td><code><a href="#SimpleBigProjectLogger">org.apache.tools.ant.listener.SimpleBigProjectLogger</a></code></td>
+ <td>Prints the project name for subprojects only, otherwise like NoBannerLogger <em>Since Ant 1.8.1</em></td>
+ <td>BuildLogger</td>
</tr>
<tr>
- <td width="33%"><code><a href="#ProfileLogger">org.apache.tools.ant.listener.ProfileLogger</a></code></td>
- <td width="33%">The default logger, with start times, end times and
+ <td><code><a href="#ProfileLogger">org.apache.tools.ant.listener.ProfileLogger</a></code></td>
+ <td>The default logger, with start times, end times and
durations added for each task and target.</td>
- <td width="34%">BuildLogger</td>
+ <td>BuildLogger</td>
</tr>
</table>
-
-
-<h3><a name="DefaultLogger">DefaultLogger</a></h3>
+<h3 id="DefaultLogger">DefaultLogger</h3>
<p>Simply run Ant normally, or:</p>
<blockquote>
<p><code>ant -logger org.apache.tools.ant.DefaultLogger</code></p>
</blockquote>
-
-
-<h3><a name="NoBannerLogger">NoBannerLogger</a></h3>
+<h3 id="NoBannerLogger">NoBannerLogger</h3>
<p>Removes output of empty target output.</p>
<blockquote>
<p><code>ant -logger org.apache.tools.ant.NoBannerLogger</code></p>
</blockquote>
-
-
-<h3><a name="MailLogger">MailLogger</a></h3>
+<h3 id="MailLogger">MailLogger</h3>
<p>The MailLogger captures all output logged through DefaultLogger (standard Ant
output) and will send success and failure messages to unique e-mail lists, with
control for turning off success or failure messages individually.</p>
<p>Properties controlling the operation of MailLogger:</p>
-<table border="1" cellspacing="1" width="100%" id="AutoNumber2">
+<table>
<tr>
- <th width="337">Property</th>
- <th width="63%">Description</th>
- <th width="63%">Required</th>
+ <th>Property</th>
+ <th>Description</th>
+ <th>Required</th>
</tr>
<tr>
- <td width="337">MailLogger.mailhost </td>
- <td width="63%">Mail server to use</td>
- <td width="63%">No, default "localhost"</td>
+ <td>MailLogger.mailhost </td>
+ <td>Mail server to use</td>
+ <td>No, default "localhost"</td>
</tr>
<tr>
- <td width="337">MailLogger.port </td>
- <td width="63%">SMTP Port for the Mail server</td>
- <td width="63%">No, default "25"</td>
+ <td>MailLogger.port </td>
+ <td>SMTP Port for the Mail server</td>
+ <td>No, default "25"</td>
</tr>
<tr>
- <td width="337">MailLogger.user</td>
- <td width="63%">user name for SMTP auth</td>
- <td width="63%">Yes, if SMTP auth is required on your SMTP server<br>
+ <td>MailLogger.user</td>
+ <td>user name for SMTP auth</td>
+ <td>Yes, if SMTP auth is required on your SMTP server<br>
the email message will be then sent using Mime and requires JavaMail</td>
</tr>
<tr>
- <td width="337">MailLogger.password</td>
- <td width="63%">password for SMTP auth</td>
- <td width="63%">Yes, if SMTP auth is required on your SMTP server<br>
+ <td>MailLogger.password</td>
+ <td>password for SMTP auth</td>
+ <td>Yes, if SMTP auth is required on your SMTP server<br>
the email message will be then sent using Mime and requires JavaMail</td>
</tr>
<tr>
- <td width="337">MailLogger.ssl</td>
- <td width="63%">on or true if ssl is needed<br>
+ <td>MailLogger.ssl</td>
+ <td>on or true if ssl is needed<br>
This feature requires JavaMail</td>
- <td width="63%">
+ <td>
no</td>
</tr>
<tr>
- <td width="337">MailLogger.from</td>
- <td width="63%">Mail "from" address</td>
- <td width="63%">Yes, if mail needs to be sent</td>
+ <td>MailLogger.from</td>
+ <td>Mail "from" address</td>
+ <td>Yes, if mail needs to be sent</td>
</tr>
<tr>
- <td width="337">MailLogger.replyto</td>
- <td width="63%">Mail "replyto" address(es), comma-separated</td>
- <td width="63%">No</td>
+ <td>MailLogger.replyto</td>
+ <td>Mail "replyto" address(es), comma-separated</td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.notify </td>
- <td width="63%">Send build failure e-mails?</td>
- <td width="63%">No, default "true"</td>
+ <td>MailLogger.failure.notify </td>
+ <td>Send build failure e-mails?</td>
+ <td>No, default "true"</td>
</tr>
<tr>
- <td width="337">MailLogger.success.notify </td>
- <td width="63%">Send build success e-mails?</td>
- <td width="63%">No, default "true"</td>
+ <td>MailLogger.success.notify </td>
+ <td>Send build success e-mails?</td>
+ <td>No, default "true"</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.to </td>
- <td width="63%">Address(es) to send failure messages to, comma-separated</td>
- <td width="63%">Yes, if failure mail is to be sent</td>
+ <td>MailLogger.failure.to </td>
+ <td>Address(es) to send failure messages to, comma-separated</td>
+ <td>Yes, if failure mail is to be sent</td>
</tr>
<tr>
- <td width="337">MailLogger.success.to </td>
- <td width="63%">Address(es) to send success messages to, comma-separated</td>
- <td width="63%">Yes, if success mail is to be sent</td>
+ <td>MailLogger.success.to </td>
+ <td>Address(es) to send success messages to, comma-separated</td>
+ <td>Yes, if success mail is to be sent</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.cc </td>
- <td width="63%">Address(es) to send failure messages to carbon copy (cc), comma-separated</td>
- <td width="63%">No</td>
+ <td>MailLogger.failure.cc </td>
+ <td>Address(es) to send failure messages to carbon copy (cc), comma-separated</td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.success.cc </td>
- <td width="63%">Address(es) to send success messages to carbon copy (cc), comma-separated</td>
- <td width="63%">No</td>
+ <td>MailLogger.success.cc </td>
+ <td>Address(es) to send success messages to carbon copy (cc), comma-separated</td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.bcc </td>
- <td width="63%">Address(es) to send failure messages to blind carbon copy (bcc), comma-separated</td>
- <td width="63%">No</td>
+ <td>MailLogger.failure.bcc </td>
+ <td>Address(es) to send failure messages to blind carbon copy (bcc), comma-separated</td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.success.bcc </td>
- <td width="63%">Address(es) to send success messages to blind carbon copy (bcc), comma-separated</td>
- <td width="63%">No</td>
+ <td>MailLogger.success.bcc </td>
+ <td>Address(es) to send success messages to blind carbon copy (bcc), comma-separated</td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.subject </td>
- <td width="63%">Subject of failed build</td>
- <td width="63%">No, default "Build Failure"</td>
+ <td>MailLogger.failure.subject </td>
+ <td>Subject of failed build</td>
+ <td>No, default "Build Failure"</td>
</tr>
<tr>
- <td width="337">MailLogger.success.subject </td>
- <td width="63%">Subject of successful build</td>
- <td width="63%">No, default "Build Success"</td>
+ <td>MailLogger.success.subject </td>
+ <td>Subject of successful build</td>
+ <td>No, default "Build Success"</td>
</tr>
<tr>
- <td width="337">MailLogger.failure.body</td>
- <td width="63%">Fixed body of the email for a failed
+ <td>MailLogger.failure.body</td>
+ <td>Fixed body of the email for a failed
build. <em>Since Ant 1.8.0</em></td>
- <td width="63%">No, default is to send the full log output.</td>
+ <td>No, default is to send the full log output.</td>
</tr>
<tr>
- <td width="337">MailLogger.success.body</td>
- <td width="63%">Fixed body of the email for a successful
+ <td>MailLogger.success.body</td>
+ <td>Fixed body of the email for a successful
build. <em>Since Ant 1.8.0</em></td>
- <td width="63%">No, default is to send the full log output.</td>
+ <td>No, default is to send the full log output.</td>
</tr>
<tr>
- <td width="337">MailLogger.mimeType</td>
- <td width="63%">MIME-Type of the message. <em>Since Ant 1.8.0</em></td>
- <td width="63%">No, default is text/plain</td>
+ <td>MailLogger.mimeType</td>
+ <td>MIME-Type of the message. <em>Since Ant 1.8.0</em></td>
+ <td>No, default is text/plain</td>
</tr>
<tr>
- <td width="337">MailLogger.charset</td>
- <td width="63%">Character set of the message. <em>Since Ant 1.8.0</em></td>
- <td width="63%">No</td>
+ <td>MailLogger.charset</td>
+ <td>Character set of the message. <em>Since Ant 1.8.0</em></td>
+ <td>No</td>
</tr>
<tr>
- <td width="337">MailLogger.starttls.enable</td>
- <td width="63%">on or true if STARTTLS should be supported
+ <td>MailLogger.starttls.enable</td>
+ <td>on or true if STARTTLS should be supported
(requires JavaMail). <em>Since Ant 1.8.0</em></td>
- <td width="63%">No, default is false</td>
+ <td>No, default is false</td>
</tr>
<tr>
- <td width="337">MailLogger.properties.file </td>
- <td width="63%">Filename of properties file that will override other values.</td>
- <td width="63%">No</td>
+ <td>MailLogger.properties.file </td>
+ <td>Filename of properties file that will override other values.</td>
+ <td>No</td>
</tr>
</table>
@@ -290,9 +284,7 @@ control for turning off success or failure messages individually.</p>
<p><code>ant -logger org.apache.tools.ant.listener.MailLogger</code></p>
</blockquote>
-
-
-<h3><a name="AnsiColorLogger">AnsiColorLogger</a></h3>
+<h3 id="AnsiColorLogger">AnsiColorLogger</h3>
<p>The AnsiColorLogger adds color to the standard Ant output
by prefixing and suffixing ANSI color code escape sequences to
@@ -307,18 +299,18 @@ in the console using applications like cat, more, etc.</p>
<p>This is designed to work on terminals that support ANSI
color codes. It works on XTerm, ETerm, Win9x Console
(with ANSI.SYS loaded.), etc.</p>
-<p><Strong>NOTE:</Strong>
+<p><strong>NOTE:</strong>
It doesn't work on WinNT and successors, even when a COMMAND.COM console loaded with
ANSI.SYS is used.</p>
<p>If the user wishes to override the default colors
with custom ones, a file containing zero or more of the
custom color key-value pairs must be created. The recognized keys
-and their default values are shown below:</p><code><pre>
+and their default values are shown below:</p><pre>
AnsiColorLogger.ERROR_COLOR=2;31
AnsiColorLogger.WARNING_COLOR=2;35
AnsiColorLogger.INFO_COLOR=2;36
AnsiColorLogger.VERBOSE_COLOR=2;32
-AnsiColorLogger.DEBUG_COLOR=2;34</pre></code>
+AnsiColorLogger.DEBUG_COLOR=2;34</pre>
<p>Each key takes as value a color combination defined as
<b>Attribute;Foreground;Background</b>. In the above example, background
value has not been used.</p>
@@ -362,12 +354,10 @@ Background is one of the following:
47 -> White</pre>
<blockquote>
-<p><code>ant -logger org.apache.tools.ant.listener.AnsiColorLogger</code></p>
+<pre>ant -logger org.apache.tools.ant.listener.AnsiColorLogger</pre>
</blockquote>
-
-
-<h3><a name="Log4jListener">Log4jListener</a></h3>
+<h3 id="Log4jListener">Log4jListener</h3>
<p><b>Deprecated:</b> Apache Log4j (1) is not developed any more. Last
release is 1.2.17 from 26-May-2012 and contains vulnerability issues.</p>
<p>Passes build events to Log4j, using the full classname's of the generator of
@@ -379,13 +369,13 @@ each build event as the category:</p>
<li>message logged - the classname of one of the above, so if a task logs a
message, its classname is the category used, and so on.</li>
</ul>
-<p>All start events are logged as INFO. Finish events are either logged as
+<p>All start events are logged as INFO. Finish events are either logged as
INFO or ERROR depending on whether the build failed during that stage. Message
events are logged according to their Ant logging level, mapping directly to a
corresponding Log4j level.</p>
<blockquote>
-<p><code>ant -listener org.apache.tools.ant.listener.Log4jListener</code></p>
+<pre>ant -listener org.apache.tools.ant.listener.Log4jListener</pre>
</blockquote>
<p>To use Log4j you will need the Log4j JAR file and a 'log4j.properties'
@@ -394,7 +384,7 @@ classpath. If the log4j.properties is in your project root folder you can
add this with <i>-lib</i> option:</p>
<blockquote>
-<pre><code>ant -listener org.apache.tools.ant.listener.Log4jListener -lib .</code></pre>
+<pre>ant -listener org.apache.tools.ant.listener.Log4jListener -lib .</pre>
</blockquote>
<p>If, for example, you wanted to capture the same information output to the
@@ -402,7 +392,7 @@ console by the DefaultLogger and send it to a file named 'build.log', you
could use the following configuration:</p>
<blockquote>
-<pre><code>log4j.rootLogger=ERROR, LogFile
+<pre>log4j.rootLogger=ERROR, LogFile
log4j.logger.org.apache.tools.ant.Project=INFO
log4j.logger.org.apache.tools.ant.Target=INFO
log4j.logger.org.apache.tools.ant.taskdefs=INFO
@@ -412,7 +402,7 @@ log4j.appender.LogFile=org.apache.log4j.FileAppender
log4j.appender.LogFile.layout=org.apache.log4j.PatternLayout
log4j.appender.LogFile.layout.ConversionPattern=[%6r] %8c{1} : %m%n
log4j.appender.LogFile.file=build.log
-</code></pre>
+</pre>
</blockquote>
<p>For more information about configuring Log4J see <a href="http://logging.apache.org/log4j/docs/documentation.html">its
@@ -432,7 +422,7 @@ to your classpath (e.g. via the <code>-lib</code> option).
(For using the bridge Ant 1.9.10/1.10.2 or higher is required.)
Translating the 1.x properties file into the 2.x xml syntax would result in
<blockquote>
-<pre><code><?xml version="1.0" encoding="UTF-8"?>
+<pre><?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Appenders>
<File name="file" fileName="build.log">
@@ -451,12 +441,10 @@ Translating the 1.x properties file into the 2.x xml syntax would result in
<Logger name="org.apache.tools.ant.taskdefs.Echo" level="WARN"/>
</Loggers>
</Configuration>
-</code></pre>
+</pre>
</blockquote>
-
-
-<h3><a name="XmlLogger">XmlLogger</a></h3>
+<h3 id="XmlLogger">XmlLogger</h3>
<p>Writes all build information out to an XML file named log.xml, or the value
of the <code>XmlLogger.file</code> property if present, when used as a
listener. When used as a logger, it writes all output to either the
@@ -472,13 +460,11 @@ If you set the property to the empty string, "", no XSLT transform
is declared at all.</p>
<blockquote>
-<p><code>ant -listener org.apache.tools.ant.XmlLogger</code><br>
-<code>ant -logger org.apache.tools.ant.XmlLogger -verbose -logfile build_log.xml</code></p>
+<pre>ant -listener org.apache.tools.ant.XmlLogger
+ant -logger org.apache.tools.ant.XmlLogger -verbose -logfile build_log.xml</pre>
</blockquote>
-
-
-<h3><a name="TimestampedLogger">TimestampedLogger</a></h3>
+<h3 id="TimestampedLogger">TimestampedLogger</h3>
<p>
Acts like the default logger, except that the final success/failure message also includes
the time that the build completed. For example:
@@ -489,12 +475,10 @@ is declared at all.</p>
<p>To use this listener, use the command:</p>
<blockquote>
-<code>ant -logger org.apache.tools.ant.listener.TimestampedLogger</code>
+<pre>ant -logger org.apache.tools.ant.listener.TimestampedLogger</pre>
</blockquote>
-
-
-<h3><a name="BigProjectLogger">BigProjectLogger</a></h3>
+<h3 id="BigProjectLogger">BigProjectLogger</h3>
<p>
This logger is designed to make examining the logs of a big build easier,
especially those run under continuous integration tools. It
@@ -545,10 +529,10 @@ Exiting project "junit"
</p>
<p>To use this listener, use the command:</p>
<blockquote>
-<code>ant -logger org.apache.tools.ant.listener.BigProjectLogger</code>
+<pre>ant -logger org.apache.tools.ant.listener.BigProjectLogger</pre>
</blockquote>
-<h3><a name="SimpleBigProjectLogger">SimpleBigProjectLogger</a></h3>
+<h3 id="SimpleBigProjectLogger">SimpleBigProjectLogger</h3>
<p>Like <code>BigProjectLogger</code>, project-qualified target names are printed,
useful for big builds with subprojects.
Otherwise it is as quiet as <code>NoBannerLogger</code>:</p>
@@ -572,18 +556,18 @@ Building jar: /sources/myapp/build/myapp.jar
BUILD SUCCESSFUL
Total time: 1 second
</pre>
-<p><b>since Ant 1.8.1</b></p>
+<p><em>since Ant 1.8.1</em></p>
<p>To use this listener, use the command:</p>
<blockquote>
-<code>ant -logger org.apache.tools.ant.listener.SimpleBigProjectLogger</code>
+<pre>ant -logger org.apache.tools.ant.listener.SimpleBigProjectLogger</pre>
</blockquote>
-<h3><a name="ProfileLogger">ProfileLogger</a></h3>
+<h3 id="ProfileLogger">ProfileLogger</h3>
<p>This logger stores the time needed for executing a task, target and the whole build and prints
these information. The output contains a timestamp when entering the build, target or task and a timestamp and the needed time when exiting.
</p>
<!-- This is the 'since' as described in the Loggers JavaDoc -->
-<p><b>since Ant 1.8.0</b></p>
+<p><em>since Ant 1.8.0</em></p>
<h4>Example</h4>
Having that buildfile
<pre>
@@ -630,9 +614,7 @@ BUILD SUCCESSFUL
Total time: 2 seconds
</pre>
-
-
-<h2><a name="dev">Writing your own</a></h2>
+<h2 id="dev">Writing your own</h2>
<p>See the <a href="develop.html#buildevents">Build Events</a> section for
developers.</p>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/platform.html
----------------------------------------------------------------------
diff --git a/manual/platform.html b/manual/platform.html
index 8b38731..0213b23 100644
--- a/manual/platform.html
+++ b/manual/platform.html
@@ -15,12 +15,12 @@
limitations under the License.
-->
<html>
-
<head>
<meta http-equiv="Content-Language" content="en-us">
<link rel="stylesheet" type="text/css" href="stylesheets/style.css">
<title>Platform Issues</title>
</head>
+<body>
<h1>Platform Issues</h1>
@@ -34,13 +34,13 @@ for example) may not work against the shipping XSL engine.
<h2>Unix and Linux</h2>
<ul>
-<li> You should use a GNU version of <tt>tar</tt> to untar the Apache
+<li> You should use a GNU version of <tt>tar</tt> to untar the Apache
Ant source tree, if you have downloaded this as a tar file. If you get
-weird errors about missing files, this is the problem.
+weird errors about missing files, this is the problem.
</li>
-<li> Ant does not preserve file permissions when a file is copied, moved or
+<li> Ant does not preserve file permissions when a file is copied, moved or
archived, because Java does not let it read or write the permissions.
- Use <tt><chmod></tt> to set permissions, and when creating a
+ Use <tt><chmod></tt> to set permissions, and when creating a
tar archive, use the <tt>mode</tt> attribute of <tt><tarfileset></tt>
to set the permissions in the tar file, or <code><apply></code> the real tar program.
</li>
@@ -50,12 +50,10 @@ of directories to build up a list of files. Unexpected things can happen.
<li> Linux on IA-64: apparently you need a larger heap than the default
one (64M) to compile big projects. If you get out of heap
errors, either increase the heap or use a forking javac. Better yet,
-use jikes for extra compilation speed.
+use jikes for extra compilation speed.
</li>
-
</ul>
-
<h2>Microsoft Windows</h2>
<p>
Windows 9x (win95, win98, win98SE and winME) are not supported in Ant1.7,
@@ -64,28 +62,29 @@ Windows 9x (win95, win98, win98SE and winME) are not supported in Ant1.7,
<p>
The Ant team has retired support for these products because they are outdated and
can expose customers to security risks. We recommend that customers who are
-still running Windows 98 or Windows Me upgrade to a newer, more secure
+still running Windows 98 or Windows Me upgrade to a newer, more secure
operating system, as soon as possible.
</p>
<p>
Customers who upgrade to Linux report improved security, richer
-functionality, and increased productivity.
+functionality, and increased productivity.
</p>
+
<h2>Microsoft Windows 2K, XP and Server 2K03 </h2>
<p>
Windows 9x (win95, win98, win98SE and winME) has a batch file system which
does not work fully with long file names, so we recommend that ant and the JDK
-are installed into directories without spaces, and with 8.3 filenames.
+are installed into directories without spaces, and with 8.3 filenames.
The Perl and Python launcher scripts do not suffer from this limitation.
</p>
<p>
-All versions of windows are usually case insensitive, although mounted
+All versions of windows are usually case insensitive, although mounted
file systems (Unix drives, Clearcase views) can be case sensitive underneath,
confusing patternsets.
</p>
<p>
-Ant can often not delete a directory which is open in an Explorer window.
+Ant can often not delete a directory which is open in an Explorer window.
There is nothing we can do about this short of spawning a program to kill
the shell before deleting directories.
Nor can files that are in use be overwritten.
@@ -96,6 +95,7 @@ Nor can files that are in use be overwritten.
</p>
<h2>Microsoft Windows Vista</h2>
+
<p>
There are reports of problems with Windows Vista security bringing up
dialog boxes asking if the user wants to run an untrusted executable
@@ -103,26 +103,28 @@ Nor can files that are in use be overwritten.
program. This is beyond Ant's control, and stems from the OS trying to provide
some illusion of security by being reluctant to run unsigned native executables.
The latest Java versions appear to resolve this problem by having signed
- binaries.
+ binaries.
</p>
-
<h2>Cygwin</h2>
-Cygwin is not an operating system; rather it is an application suite
-running under Windows and providing some UNIX like functionality. Sun has
-not created any specific Java Development Kit or Java Runtime Environment for
-cygwin. See this link :
-<a href="http://www.inonit.com/cygwin/faq/">http://www.inonit.com/cygwin/faq/</a> .
-Only Windows path
-names are supported by JDK and JRE tools under Windows or cygwin. Relative path
-names such as "src/org/apache/tools" are supported, but Java tools do not
+<p>
+Cygwin is not an operating system; rather it is an application suite
+running under Windows and providing some UNIX like functionality. Sun has
+not created any specific Java Development Kit or Java Runtime Environment for
+cygwin. See this link :
+<a href="http://www.inonit.com/cygwin/faq/">http://www.inonit.com/cygwin/faq/</a> .
+Only Windows path
+names are supported by JDK and JRE tools under Windows or cygwin. Relative path
+names such as "src/org/apache/tools" are supported, but Java tools do not
understand /cygdrive/c to mean c:\.
+</p>
<p>
-The utility cygpath (used industrially in the ant script to support cygwin) can
+The utility cygpath (used industrially in the ant script to support cygwin) can
convert cygwin path names to Windows.
-You can use the <code><exec></code> task in ant to convert cygwin paths to Windows path, for
-instance like that :
+You can use the <code><exec></code> task in ant to convert cygwin paths to Windows path, for
+instance like that:
+</p>
<pre>
<property name="some.cygwin.path" value="/cygdrive/h/somepath"/>
<exec executable="cygpath" outputproperty="windows.pathname">
@@ -131,48 +133,50 @@ instance like that :
</exec>
<echo message="${windows.pathname}"/>
</pre>
-
+<p>
We get lots of support calls from Cygwin users. Either it is incredibly
popular, or it is trouble. If you do use it, remember that Java is a
Windows application, so Ant is running in a Windows process, not a
-Cygwin one. This will save us having to mark your bug reports as invalid.
+Cygwin one. This will save us having to mark your bug reports as invalid.
+</p>
<h2>Apple MacOS X</h2>
+<p>
MacOS X is the first of the Apple platforms that Ant supports completely;
-it is treated like any other Unix.
+it is treated like any other Unix.
+</p>
<h2>Novell Netware</h2>
<p>To give the same level of sophisticated control as Ant's startup scripts on other platforms, it was decided to make the main ant startup on NetWare be via a Perl Script, "runant.pl". This is found in the bin directory (for instance - bootstrap\bin or dist\bin).</p>
-<p>One important item of note is that you need to set up the following to run ant:</p>
+<p>One important item of note is that you need to set up the following to run Ant:</p>
<ul><li><code>CLASSPATH</code> - put ant.jar and any other needed jars on the system classpath.</li>
- <li><code>ANT_OPTS</code> - On NetWare, <code>ANT_OPTS</code> needs to include a parameter of the form, <nobr>"-envCWD=<code>ANT_HOME</code>"</nobr>, with <code>ANT_HOME</code> being the fully expanded location of Ant, <b>not</b> an environment variable. This is due to the fact that the NetWare System Console has no notion of a current working directory.</li>
+ <li><code>ANT_OPTS</code> - On NetWare, <code>ANT_OPTS</code> needs to include a parameter of the form, "<code>-envCWD=<i>ANT_HOME</i></code>", with <code><i>ANT_HOME</i></code> being the fully expanded location of Ant, <b>not</b> an environment variable. This is due to the fact that the NetWare System Console has no notion of a current working directory.</li>
</ul>
<p>It is suggested that you create up an ant.ncf that sets up these parameters, and calls <code>perl ANT_HOME/dist/bin/runant.pl</code></p>
-<p>The following is an example of such an NCF file(assuming ant is installed in <nobr>'sys:/apache-ant/'):</nobr></p>
-<code>
- envset CLASSPATH=SYS:/apache-ant/bootstrap/lib/ant.jar<br>
- envset CLASSPATH=$CLASSPATH;SYS:/apache-ant/lib/optional/junit.jar <br>
- envset CLASSPATH=$CLASSPATH;SYS:/apache-ant/bootstrap/lib/optional.jar <br>
-<br>
- setenv ANT_OPTS=-envCWD=sys:/apache-ant <br>
- envset ANT_OPTS=-envCWD=sys:/apache-ant <br>
- setenv ANT_HOME=sys:/apache-ant/dist/lib <br>
- envset ANT_HOME=sys:/apache-ant/dist/lib <br>
-<br>
- perl sys:/apache-ant/dist/bin/runant.pl <br>
-</code>
+<p>The following is an example of such an NCF file (assuming Ant is installed in <code>'sys:/apache-ant/'</code>):</p>
+<pre>
+ envset CLASSPATH=SYS:/apache-ant/bootstrap/lib/ant.jar
+ envset CLASSPATH=$CLASSPATH;SYS:/apache-ant/lib/optional/junit.jar
+ envset CLASSPATH=$CLASSPATH;SYS:/apache-ant/bootstrap/lib/optional.jar
+
+ setenv ANT_OPTS=-envCWD=sys:/apache-ant
+ envset ANT_OPTS=-envCWD=sys:/apache-ant
+ setenv ANT_HOME=sys:/apache-ant/dist/lib
+ envset ANT_HOME=sys:/apache-ant/dist/lib
+
+ perl sys:/apache-ant/dist/bin/runant.pl
+</pre>
<p>Ant works on JVM version 1.3 or higher. You may have some luck running it on JVM 1.2, but serious problems have been found running Ant on JVM 1.1.7B. These problems are caused by JVM bugs that will not be fixed.</p>
<p>JVM 1.3 is supported on Novell NetWare versions 5.1 and higher.</p>
-
<h2>Other platforms</h2>
-Support for other platforms is not guaranteed to be complete, as certain
+Support for other platforms is not guaranteed to be complete, as certain
techniques to hide platform details from build files need to be written and
tested on every particular platform. Contributions in this area are welcome.
-
+</body>
</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/projecthelper.html
----------------------------------------------------------------------
diff --git a/manual/projecthelper.html b/manual/projecthelper.html
index 2e43f79..4961694 100644
--- a/manual/projecthelper.html
+++ b/manual/projecthelper.html
@@ -25,7 +25,7 @@
<body>
<h1>The Apache Ant frontend: ProjectHelper</h1>
-<h2><a name="definition">What is a ProjectHelper?</a></h2>
+<h2 id="definition">What is a ProjectHelper?</h2>
<p>
The <code>ProjectHelper</code> in Apache Ant is responsible for parsing the build file
@@ -53,7 +53,7 @@ write different build files in different languages and have them import each
other.
</p>
-<h2><a name="repository">How is Ant is selecting the proper ProjectHelper</a></h2>
+<h2 id="repository">How is Ant is selecting the proper ProjectHelper</h2>
<p>
Ant knows about several implementations of <code>ProjectHelper</code>
@@ -61,7 +61,7 @@ and has to decide which to use for each build file.
</p>
<p>At startup Ant lists the all implementations found and keeps them
-in the same order they've been found in an internal 'repository':
+ in the same order they've been found in an internal 'repository':</p>
<ul>
<li>the first to be searched for is the one declared by the system property
<code>org.apache.tools.ant.ProjectHelper</code> (see
@@ -76,7 +76,7 @@ in the same order they've been found in an internal 'repository':
<li>last but not least it will add its default <code>ProjectHelper</code>
that can parse classical build.xml files.</li>
</ul>
-In case of an error while trying to instantiate a <code>ProjectHelper</code>, Ant
+<p>In case of an error while trying to instantiate a <code>ProjectHelper</code>, Ant
will log an error but won't stop. If you want further debugging
info about the <code>ProjectHelper</code> internal 'repository', use the <b>system</b>
property <code>ant.project-helper-repo.debug</code> and set it to
@@ -97,7 +97,7 @@ a default input file. It will iterate over list of <code>ProjectHelper</code>s
and will select the first one that expects a default file that actually exist.
</p>
-<h2><a name="writing">Writing your own ProjectHelper</a></h2>
+<h2 id="writing">Writing your own ProjectHelper</h2>
<p>
The class <code>org.apache.tools.ant.ProjectHelper</code> is the API expected to
@@ -111,6 +111,7 @@ constructor with no arguments.
<p>
There are some functions that will help you define what your helper is
capable of and what is is expecting:
+</p>
<ul>
<li><code>getDefaultBuildFile()</code>: defines which file name is expected if
none provided</li>
@@ -125,11 +126,11 @@ capable of and what is is expecting:
descriptor if your implementation returned <code>true</code>
for the previous method.</li>
</ul>
-</p>
<p>
Now that you have your implementation ready, you have to declare it to Ant. Three
solutions here:
+</p>
<ul>
<li>use the system property <code>org.apache.tools.ant.ProjectHelper</code>
(see also the <a href="running.html#sysprops">Java System Properties</a>);</li>
@@ -143,8 +144,6 @@ solutions here:
'repository'. Then your helper can be used on the next call to the
<a href="Tasks/import.html">import</a> task.</li>
</ul>
-</p>
</body>
</html>
-
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/properties.html
----------------------------------------------------------------------
diff --git a/manual/properties.html b/manual/properties.html
index 226972a..54d231d 100644
--- a/manual/properties.html
+++ b/manual/properties.html
@@ -43,14 +43,14 @@
the <a href="Tasks/ant.html">ant</a>, antcall or subant tasks
and make it available to the calling build process, though.</p>
- <p>Starting with Ant 1.8.0
+ <p><em>Since Ant 1.8.0</em>
the <a href="Tasks/local.html">local</a> task can be used to
create properties that are locally scoped to a target or
a <a href="Tasks/sequential.html">sequential</a> element like
the one of the <a href="Tasks/macrodef.html">macrodef</a>
task.</p>
- <h2><a name="built-in-props">Built-in Properties</a></h2>
+ <h2 id="built-in-props">Built-in Properties</h2>
<p>Ant provides access to all system properties as if they had been
defined using a <code><property></code> task. For
@@ -105,7 +105,7 @@ ant.library.dir the directory that has been used to load Ant's
jars from. In most cases this is ANT_HOME/lib.
</pre>
- <h1><a name="propertyHelper">PropertyHelpers</a></h1>
+ <h1 id="propertyHelper">PropertyHelpers</h1>
<p>Ant's property handling is accomplished by an instance of
<code>org.apache.tools.ant.PropertyHelper</code> associated with
@@ -210,7 +210,6 @@ public class ToStringEvaluator implements PropertyHelper.PropertyEvaluator {
}
</pre>
-
<h1>Property Expansion</h1>
<p>When Ant encounters a construct <code>${some-text}</code> the
@@ -238,7 +237,7 @@ public class ToStringEvaluator implements PropertyHelper.PropertyEvaluator {
<p>if the property <code>builddir</code> has the
value <code>build/classes</code>.</p>
-
+
<p>In order to maintain backward compatibility with older Ant
releases, a single '$' character encountered apart from a
property-like construct (including a matched pair of french
@@ -284,8 +283,8 @@ public class ToStringEvaluator implements PropertyHelper.PropertyEvaluator {
Antlib</a> provides a few interesting evaluators but there are
also a few built-in ones.</p>
- <h3><a name="toString">Getting the value of a Reference with
- ${toString:}</a></h3>
+ <h3 id="toString">Getting the value of a Reference with
+ ${toString:}</h3>
<p>Any Ant type which has been declared with a reference can also
its string value extracted by using the <code>${toString:}</code>
@@ -305,8 +304,8 @@ public class ToStringEvaluator implements PropertyHelper.PropertyEvaluator {
<p>There is no guarantee that external types provide meaningful
information in such a situation</p>
- <h3><a name="ant.refid">Getting the value of a Reference with
- ${ant.refid:}</a></h3>
+ <h3 id="ant.refid">Getting the value of a Reference with
+ ${ant.refid:}</h3>
<p>Any Ant type which has been declared with a reference can also be
used as a property by using the <code>${ant.refid:}</code>
@@ -332,7 +331,7 @@ public void setAttr(Resource r) { ... }
<my:task attr="${ant.refid:anturl}"/>
</pre>
- <h2><a name="if+unless">If/Unless Attributes</a></h2>
+ <h2 id="if+unless">If/Unless Attributes</h2>
<p>
The <code><target></code> element and various tasks (such as
<code><fail></code>) and task elements (such as <code><test></code>
@@ -357,7 +356,7 @@ public void setAttr(Resource r) { ... }
<target name="lots-of-stuff" depends="use-file,other-unconditional-stuff"/>
</pre>
<p>
- As of Ant 1.8.0, you may instead use property expansion; a value of
+ <em>Since Ant 1.8.0</em>, you may instead use property expansion; a value of
<tt>true</tt> (or <tt>on</tt> or <tt>yes</tt>) will enable the
item, while <tt>false</tt> (or <tt>off</tt> or <tt>no</tt>) will
disable it. Other values are still assumed to be property
@@ -402,3 +401,4 @@ public void setAttr(Resource r) { ... }
</pre>
</body>
+</html>
http://git-wip-us.apache.org/repos/asf/ant/blob/5266b79b/manual/proxy.html
----------------------------------------------------------------------
diff --git a/manual/proxy.html b/manual/proxy.html
index 13ef6e8..f614803 100644
--- a/manual/proxy.html
+++ b/manual/proxy.html
@@ -31,7 +31,6 @@ Consult your IDE documentation for IDE-specific information upon proxy setup.
</p>
<p>
-
All tasks and threads running in Ant's JVM share the same HTTP/FTP/Socks
proxy configuration.
</p>
@@ -56,13 +55,11 @@ proxy configuration.
</p>
-
-
-<h3>Java1.5+ proxy support (new for Ant1.7)</h3>
+<h3>Java1.5+ proxy support (<em>since Ant 1.7</em>)</h3>
<p>
When Ant starts up, if the <code>-autoproxy</code>
command is supplied, Ant sets the
- <code>java.net.useSystemProxies</code> system property. This tells
+ <code>java.net.useSystemProxies</code> system property. This tells
a Java1.5+ JVM to use the current set of property settings of the host
environment. Other JVMs, such as the Kaffe and Apache Harmony runtimes,
may also use this property in future.
@@ -91,8 +88,8 @@ The <code>java.net.useSystemProxies</code> is checked only
once, at startup time, the other checks (registry, gconf, system properties) are done
dynamically whenever needed (socket connection, URL connection etc..).
</p>
-<h5>Windows</h5>
+<h5>Windows</h5>
<p>
The JVM goes straight to the registry, bypassing WinInet, as it is not
present/consistent on all supported Windows platforms (it is part of IE,
@@ -100,7 +97,6 @@ really). Java 7 may use the Windows APIs on the platforms when it is present.
</p>
<h5>Linux</h5>
-
<p>
The JVM uses the gconf library to look at specific entries.
The GConf-2 settings used are:
@@ -128,7 +124,6 @@ If you are using KDE or another GUI than Gnome, you can still use the
<code>gconf-editor</code> tool to add these entries.
</p>
-
<h3>Manual JVM options</h3>
<p>
Any JVM can have its proxy options explicitly configured by passing
@@ -139,7 +134,7 @@ If you are using KDE or another GUI than Gnome, you can still use the
</p>
<p>
For bash:
-</p>
+</p>
<pre>
export ANT_OPTS="-Dhttp.proxyHost=proxy -Dhttp.proxyPort=8080"
</pre>
@@ -153,30 +148,29 @@ by all continuous integration tools running on the system that call Ant via the
command line.
</p>
<p>
- For Windows, set the <code>ANT_OPTS</code> environment variable in the appropriate "My Computer"
+ For Windows, set the <code>ANT_OPTS</code> environment variable in the appropriate "My Computer"
properties dialog box (winXP), "Computer" properties (Vista)
</p>
<p>
- This mechanism works across Java versions, is cross-platform and reliable.
+ This mechanism works across Java versions, is cross-platform and reliable.
Once set, all build files run via the command line will automatically have
their proxy setup correctly, without needing any build file changes. It also
apparently overrides Ant's automatic proxy settings options.
</p>
-<p>
+<p>
It is limited in the following ways:
-</p>
+</p>
<ol>
<li>Does not work under IDEs. These need their own proxy settings changed</li>
<li>Not dynamic enough to deal with laptop configuration changes.</li>
</ol>
-
<h3>SetProxy Task</h3>
<p>
The <a href="Tasks/setproxy.html">setproxy task</a> can be used to
- explicitly set a proxy in a build file. This manipulates the many proxy
- configuration properties of a JVM, and controls the proxy settings for all
- network operations in the same JVM from that moment.
+ explicitly set a proxy in a build file. This manipulates the many proxy
+ configuration properties of a JVM, and controls the proxy settings for all
+ network operations in the same JVM from that moment.
</p>
<p>
If you have a build file that is only to be used in-house, behind a firewall, on
@@ -186,10 +180,9 @@ command line.
the many possible proxy options of different users (none, HTTP, SOCKS).
</p>
-
<p>
Note that proxy configurations set with this task will probably override
- any set by other mechanisms. It can also be used with fancy tricks to
+ any set by other mechanisms. It can also be used with fancy tricks to
only set a proxy if the proxy is considered reachable:
</p>
@@ -214,10 +207,10 @@ command line.
<h3>Custom ProxySelector implementations</h3>
<p>
- As Java lets developers write their own ProxySelector implementations, it
+ As Java lets developers write their own ProxySelector implementations, it
is theoretically possible for someone to write their own proxy selector class that uses
different policies to determine proxy settings. There is no explicit support
- for this in Ant, and it has not, to the team's knowledge, been attempted.
+ for this in Ant, and it has not, to the team's knowledge, been attempted.
</p>
<p>
This could be the most flexible of solutions, as one could easily imagine
@@ -239,14 +232,15 @@ command line.
<code>fork="true"</code> will pick up the Ant's settings. If you need
different values, set <code>fork="false"</code> and provide the values
in <code><sysproperty></code> elements.
-</p>
+</p>
+<p>
If you wish to have
- a forked process pick up the Ant's settings, use the
+ a forked process pick up the Ant's settings, use the
<a href="Types/propertyset.html"><code><syspropertyset></code></a>
element to propagate the normal proxy settings. The following propertyset
is a datatype which can be referenced in a <code><java></code> task to
pass down the current values.
-
+
</p>
<pre>
<propertyset id="proxy.properties">