@@ -13,7 +13,7 @@
href="http://ant.apache.org/">http://ant.apache.org/</a>.
If you like living on the edge, you can download the latest version from <a
href="http://cvs.apache.org/builds/jakarta- ant/nightly/">http://cvs.apache.org/builds/jakarta- ant/nightly/</a>.</p>
href="http://cvs.apache.org/builds/ant/nightly/">http://cvs.apache.org/builds/ant/nightly/</a>.</p>
<h3>Source Edition</h3>
<p>If you prefer the source edition, you can download the source for the latest Ant release from <a href="http://ant.apache.org/srcdownload.cgi">http://ant.apache.org/srcdownload.cgi</a>.
@@ -21,39 +21,39 @@ href="http://cvs.apache.org/builds/jakarta-ant/nightly/">http://cvs.apache.org/b
Again, if you prefer the edge, you can access
the code as it is being developed via CVS. The Jakarta website has details on
<a href="http://jakarta.apache.org/site/cvsindex.html" target="_top">accessing CVS</a>. Please checkout the
jakarta- ant module.
ant module.
See the section <a href="#buildingant">Building Ant</a> on how to
build Ant from the source code.
You can also access the
<a href="http://cvs.apache.org/viewcvs/jakarta- ant/" target="_top">
You can also access the
<a href="http://cvs.apache.org/viewcvs/ant/" target="_top">
Ant CVS repository</a> on-line. </p>
<hr>
<h2><a name="sysrequirements">System Requirements</a></h2>
Ant has been used successfully on many platforms, including Linux,
commercial flavours of Unix such as Solaris and HP-UX,
Windows 9x and NT, Novell Netware 6 and MacOS X.
Windows 9x and NT, Novell Netware 6 and MacOS X.
<p>
To build and use Ant, you must have a JAXP-compliant XML parser installed and
To build and use Ant, you must have a JAXP-compliant XML parser installed and
available on your classpath.</p>
<p>
The binary distribution of Ant includes the latest version of the
<a href="http://xml.apache.org/xerces2-j/index.html">Apache Xerces2</a> XML parser.
Please see
<a href="http://java.sun.com/xml/" target="_top">http://java.sun.com/xml/</a>
for more information about JAXP.
<a href="http://xml.apache.org/xerces2-j/index.html">Apache Xerces2</a> XML parser.
Please see
<a href="http://java.sun.com/xml/" target="_top">http://java.sun.com/xml/</a>
for more information about JAXP.
If you wish to use a different JAXP-compliant parser, you should remove
<code>xercesImpl.jar</code> and <code>xml-apis.jar</code>
from Ant's <code>lib</code> directory.
You can then either put the jars from your preferred parser into Ant's
You can then either put the jars from your preferred parser into Ant's
<code>lib</code> directory or put the jars on the system classpath.</p>
<p>
For the current version of Ant, you will also need a JDK installed on
your system, version 1.1 or later. Some tasks work better on post-1.1 systems;
some tasks only work on Java 1.2 and successors.
some tasks only work on Java 1.2 and successors.
A future version of Ant -Ant 2.0- will require JDK 1.2 or later, though
Ant 1.x strives to retain 1.1 compatibility.
</p><p>
@@ -62,7 +62,7 @@ compiler is supported.
</p>
<p>
<strong>Note #2: </strong>If a JDK is not present, only the JRE runtime, then many tasks will not work.
</p>
</p>
<hr>
<h2><a name="installing">Installing Ant</a></h2>
<p>The binary distribution of Ant consists of the following directory layout:
@@ -85,11 +85,11 @@ compiler is supported.
// - ... and more ;-)
</pre>
Only the <code>bin</code> and <code>lib</code> directories are
required to run Ant.
Only the <code>bin</code> and <code>lib</code> directories are
required to run Ant.
To install Ant, choose a directory and copy the distribution
file there. This directory will be known as ANT_HOME.
file there. This directory will be known as ANT_HOME.
</p>
<table width="80%">
@@ -124,7 +124,7 @@ installed in a <b>short</b>, 8.3 path, such as C:\Ant. </i>
<h3>Setup</h3>
<p>
Before you can run ant there is some additional set up you
Before you can run ant there is some additional set up you
will need to do:</p>
<ul>
<li>Add the <code>bin</code> directory to your path.</li>
@@ -137,19 +137,19 @@ Windows NT/2000) - but it is better to not rely on this behavior.</li>
This should be set to the directory where your JDK is installed.</li>
</ul>
<p><strong>Note:</strong> Do not install Ant's ant.jar file into the lib/ext
directory of the JDK/JRE. Ant is an application, whilst the extension
directory is intended for JDK extensions. In particular there are security
directory of the JDK/JRE. Ant is an application, whilst the extension
directory is intended for JDK extensions. In particular there are security
restrictions on the classes which may be loaded by an extension.</p>
<h3><a name="optionalTasks">Optional Tasks</a></h3>
<p>Ant supports a number of optional tasks. An optional task is a task which
typically requires an external library to function. The optional tasks are
typically requires an external library to function. The optional tasks are
packaged together with the core Ant tasks.</p>
<p>The external libraries required by each of the optional tasks is detailed
in the <a href="#librarydependencies">Library Dependencies</a> section. These external
libraries may either be placed in Ant's lib directory, where they will be picked up
automatically, or made available on the system CLASSPATH environment variable.
automatically, or made available on the system CLASSPATH environment variable.
</p>
<h3>Windows</h3>
@@ -177,19 +177,19 @@ set path=( $path $ANT_HOME/bin )</pre>
<p>There are lots of variants that can be used to run Ant. What you need is at
least the following:</p>
<ul>
<li>The classpath for Ant must contain <code>ant.jar</code> and any jars/classes
<li>The classpath for Ant must contain <code>ant.jar</code> and any jars/classes
needed for your chosen JAXP-compliant XML parser.</li>
<li>When you need JDK functionality
(such as for the <a href="CoreTasks/javac.html">javac</a> task or the
<a href="CoreTasks/rmic.html">rmic</a> task), then for JDK 1.1, the <code>classes.zip</code>
file of the JDK must be added to the classpath; for JDK 1.2 or JDK 1.3, <code>tools.jar</code>
must be added. The scripts supplied with Ant,
in the <code>bin</code> directory, will add
in the <code>bin</code> directory, will add
the required JDK classes automatically, if the <code>JAVA_HOME</code>
environment variable is set.</li>
<li>When you are executing platform-specific applications, such as the
<a href="CoreTasks/exec.html">exec</a> task or the
<li>When you are executing platform-specific applications, such as the
<a href="CoreTasks/exec.html">exec</a> task or the
<a href="CoreTasks/cvs.html">cvs</a> task, the property <code>ant.home</code>
must be set to the directory containing where you installed Ant. Again
this is set by the Ant scripts to the value of the ANT_HOME environment
@@ -201,10 +201,10 @@ to ant. Some of the scripts also read in an extra script stored
in the users home directory, which can be used to set such options. Look
at the source for your platform's invocation script for details.
<hr>
<hr>
<h2><a name="buildingant">Building Ant</a></h2>
<p>To build Ant from source, you can either install the Ant source distribution
or checkout the jakarta- ant module from CVS.</p>
or checkout the ant module from CVS.</p>
<p>Once you have installed the source, change into the installation
directory.</p>
@@ -222,7 +222,7 @@ for a list of jar requirements for various features.
Note that this will make the auxiliary jars
available for the building of Ant only. For running Ant you will
still need to
make the jars available as described under
make the jars available as described under
<a href="#installing">Installing Ant</a>.</p>
<p>Your are now ready to build Ant:</p>
@@ -236,11 +236,11 @@ make the jars available as described under
<p>The above action does the following:</p>
<ul>
<li>If necessary it will bootstrap the Ant code. Bootstrapping involves the manual
<li>If necessary it will bootstrap the Ant code. Bootstrapping involves the manual
compilation of enough Ant code to be able to run Ant. The bootstrapped Ant is
used for the remainder of the build steps. </li>
<li>Invokes the bootstrapped Ant with the parameters passed to the build script. In
<li>Invokes the bootstrapped Ant with the parameters passed to the build script. In
this case, these parameters define an Ant property value and specify the "dist" target
in Ant's own <code>build.xml</code> file.</li>
</ul>
@@ -263,9 +263,9 @@ You can avoid the lengthy Javadoc step, if desired, with:
<p><code>build install-lite</code> (<i>Windows</i>)</p>
<p><code>build.sh install-lite</code> (<i>Unix</i>)</p>
</blockquote>
This will only install the <code>bin</code> and <code>lib</code> directories.
<p>Both the <code>install</code> and
<code>install-lite</code> targets will overwrite
This will only install the <code>bin</code> and <code>lib</code> directories.
<p>Both the <code>install</code> and
<code>install-lite</code> targets will overwrite
the current Ant version in <code>ANT_HOME</code>.</p>
<hr>
@@ -288,7 +288,7 @@ Installing Ant / Optional Tasks</a> section above.</p>
<td>An XSL transformer like Xalan or XSL:P</td>
<td>style task</td>
<td><a href="http://xml.apache.org/xalan-j/index.html"
target="_top">http://xml.apache.org/xalan-j/index.html</a> for Xalan.<br>
target="_top">http://xml.apache.org/xalan-j/index.html</a> for Xalan.<br>
XSL:P used to live at <a href="http://www.clc-marketing.com/xslp/"
target="_top">http://www.clc-marketing.com/xslp/</a>, but the link
doesn't work any longer and we are not aware of a replacement site.</td>
@@ -384,7 +384,7 @@ Installing Ant / Optional Tasks</a> section above.</p>
</tr>
<tr>
<td>bcel.jar</td>
<td>classfileset data type,
<td>classfileset data type,
JavaClassHelper used by the ClassConstants filter reader and
optionally used by ejbjar for dependency determination
</td>
Stefan Bodewig