The final version of Ant 1.5.1 is now available for
download. If you have any feedback on this release, feel free to join the
discussion on the ant-dev and ant-user mailing lists.
The first beta version of Ant 1.5.1 is now available for
download. If you have any feedback on the beta feel free to join the
discussion on the ant-dev and ant-user mailing lists.
July 15, 2002 - Fix for Cygwin problem in wrapper script available
The wrapper script of Ant 1.5 needs to be replaced with a new
version for Cygwin users. See the FAQ for details.
@@ -143,68 +240,48 @@
download. If you have any feedback on this release, feel free to join the
discussion on the ant-dev and ant-user mailing lists.
-
The third beta version of Ant 1.5 is now available for
download. If you have any feedback on the beta feel free to join the
discussion on the ant-dev and ant-user mailing lists.
The second beta version of Ant 1.5 is now available for
download. If you have any feedback on the beta feel free to join the
discussion on the ant-dev and ant-user mailing lists.
The first beta version of Ant 1.5 is now available for
download. If you have any feedback on the beta feel free to join the
discussion on the ant-dev and ant-user mailing lists.
Java 1.4 has now been released by Sun. The latest Ant source supports
@@ -254,45 +321,30 @@
on Java 1.4 over Windows XP. If you have problems running Ant 1.4.1 on WinXP/Java 1.4,
please use a recent build or compile your own version from the source tree.
A commented version of the collected user requirements is now
available here - it is not
complete as some details still have to be defined, but it should
@@ -301,30 +353,20 @@
and prototypes. Several people are working on prototypes (that
can be found in Ant's CVS module in the proposals directory) and
discussion is going on on the Ant-Dev mailing list.
Ant has been in use for quite some time and has been used in ways never conceived when it
was originally written. While Ant 1.x has continued to sucessfully evolve and grow, there
are a number of limitations and inconsistencies that are now apparent and which need to
@@ -362,25 +404,34 @@
Ant-Dev mailing list and contribute
your ideas.
Use the links below to download a binary distribution of Ant from
one of our mirrors. You mustverify the integrity of the
@@ -110,17 +216,12 @@ Thus they must be untarred with a GNU compatible version of
You are currently using [preferred]. If you encounter a
problem with this mirror, please select another mirror. If all
mirrors are failing, there are backup mirrors (at the end of
@@ -139,17 +240,12 @@ Other mirrors:
-
Older releases of Ant can be found here. Those
releases are only provided as zip archives that can be
extracted by jar xf archive.zip - we highly
recommend to not use those releases but upgrade to Ant's latest release.
It is essential that you verify the integrity of the downloaded
files using the PGP or MD5 signatures.
The PGP signatures can be verified using PGP or GPG. First
@@ -237,25 +318,34 @@ included in many unix distributions. It is also available as part of
Textutils. Windows users can get binary md5 programs from here, here, or
here.
We highly recommend to verify the PGP signature, though.
-
+
+
+
+
+
diff --git a/proposal/ant-site/anakia/docs/breadcrumbs.js b/proposal/ant-site/anakia/docs/breadcrumbs.js
new file mode 100644
index 000000000..f03dabb45
--- /dev/null
+++ b/proposal/ant-site/anakia/docs/breadcrumbs.js
@@ -0,0 +1,257 @@
+/*
+
+ ============================================================================
+ The Apache Software License, Version 1.1
+ ============================================================================
+
+ Copyright (C) 2002 The Apache Software Foundation. All rights reserved.
+
+ Redistribution and use in source and binary forms, with or without modifica-
+ tion, are permitted provided that the following conditions are met:
+
+ 1. Redistributions of source code must retain the above copyright notice,
+ this list of conditions and the following disclaimer.
+
+ 2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+ 3. The end-user documentation included with the redistribution, if any, must
+ include the following acknowledgment: "This product includes software
+ developed by the Apache Software Foundation (http://www.apache.org/)."
+ Alternately, this acknowledgment may appear in the software itself, if
+ and wherever such third-party acknowledgments normally appear.
+
+ 4. The names "Jakarta", "Avalon", "Excalibur" and "Apache Software Foundation"
+ must not be used to endorse or promote products derived from this software
+ without prior written permission. For written permission, please contact
+ apache@apache.org.
+
+ 5. Products derived from this software may not be called "Apache", nor may
+ "Apache" appear in their name, without prior written permission of the
+ Apache Software Foundation.
+
+ THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
+ INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+ FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
+ APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
+ INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU-
+ DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
+ OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+ This software consists of voluntary contributions made by many individuals
+ on behalf of the Apache Software Foundation. For more information on the
+ Apache Software Foundation, please see .
+
+*/
+
+/**
+ * This script, when included in a html file, builds a neat breadcrumb trail
+ * based on its url. That is, if it doesn't contains bugs (I'm relatively
+ * sure it does).
+ *
+ * Typical usage:
+ *
+ *
+ *@author Leo Simons (main author)
+ *@author Nicola Ken Barozzi (integration in skin)
+ *@created July 12, 2002
+ *@version 1.0
+ */
+
+/* ========================================================================
+ CONSTANTS
+ ======================================================================== */
+
+/**
+ * Two-dimensional array containing extra crumbs to place at the front of
+ * the trail. Specify first the name of the crumb, then the URI that belongs
+ * to it. You'll need to modify this for every domain or subdomain where
+ * you use this script (you can leave it as an empty array if you wish)
+ */
+var PREPREND_CRUMBS = new Array();
+ if(!("apache"=="")){
+ PREPREND_CRUMBS.push( new Array( "apache", "http://www.apache.org/" ) );
+ }
+ if(!("xml.apache"=="")){
+ PREPREND_CRUMBS.push( new Array( "ant.apache", "http://ant.apache.org/" ) );
+ }
+ if(!(""=="")){
+ PREPREND_CRUMBS.push( new Array( "", "" ) );
+ }
+
+/**
+ * String to include between crumbs:
+ */
+var DISPLAY_SEPARATOR = " > ";
+/**
+ * String to include at the beginning of the trail
+ */
+var DISPLAY_PREPREND = "";
+/**
+ * String to include at the end of the trail
+ */
+var DISPLAY_POSTPREND = "";
+
+/**
+ * CSS Class to use for a single crumb:
+ */
+var CSS_CLASS_CRUMB = "breadcrumb";
+
+/**
+ * CSS Class to use for the complete trail:
+ */
+var CSS_CLASS_TRAIL = "breadcrumbTrail";
+
+/**
+ * CSS Class to use for crumb separator:
+ */
+var CSS_CLASS_SEPARATOR = "crumbSeparator";
+
+/**
+ * Array of strings containing common file extensions. We use this to
+ * determine what part of the url to ignore (if it contains one of the
+ * string specified here, we ignore it).
+ */
+var FILE_EXTENSIONS = new Array( ".html", ".htm", ".jsp", ".php", ".php3", ".php4" );
+
+/**
+ * String that separates parts of the breadcrumb trail from each other.
+ * When this is no longer a slash, I'm sure I'll be old and grey.
+ */
+var PATH_SEPARATOR = "/";
+
+/* ========================================================================
+ UTILITY FUNCTIONS
+ ======================================================================== */
+/**
+ * Capitalize first letter of the provided string and return the modified
+ * string.
+ */
+function sentenceCase( string )
+{
+ var lower = string.toLowerCase();
+ return lower.substr(0,1).toUpperCase() + lower.substr(1);
+}
+
+/**
+ * Returns an array containing the names of all the directories in the
+ * current document URL
+ */
+function getDirectoriesInURL()
+{
+ var trail = document.location.pathname.split( PATH_SEPARATOR );
+
+ // check whether last section is a file or a directory
+ var lastcrumb = trail[trail.length-1];
+ for( var i = 0; i < FILE_EXTENSIONS.length; i++ )
+ {
+ if( lastcrumb.indexOf( FILE_EXTENSIONS[i] ) )
+ {
+ // it is, remove it and send results
+ return trail.slice( 1, trail.length-1 );
+ }
+ }
+
+ // it's not; send the trail unmodified
+ return trail.slice( 1, trail.length );
+}
+
+/* ========================================================================
+ BREADCRUMB FUNCTIONALITY
+ ======================================================================== */
+/**
+ * Return a two-dimensional array describing the breadcrumbs based on the
+ * array of directories passed in.
+ */
+function getBreadcrumbs( dirs )
+{
+ var prefix = "/";
+ var postfix = "/";
+
+ // the array we will return
+ var crumbs = new Array();
+
+ if( dirs != null )
+ {
+ for( var i = 0; i < dirs.length; i++ )
+ {
+ prefix += dirs[i] + postfix;
+ crumbs.push( new Array( dirs[i], prefix ) );
+ }
+ }
+
+ // preprend the PREPREND_CRUMBS
+ if(PREPREND_CRUMBS.length > 0 )
+ {
+ return PREPREND_CRUMBS.concat( crumbs );
+ }
+
+ return crumbs;
+}
+
+/**
+ * Return a string containing a simple text breadcrumb trail based on the
+ * two-dimensional array passed in.
+ */
+function getCrumbTrail( crumbs )
+{
+ var xhtml = DISPLAY_PREPREND;
+
+ for( var i = 0; i < crumbs.length; i++ )
+ {
+ xhtml += '';
+ xhtml += sentenceCase( crumbs[i][0] ) + '';
+ if( i != (crumbs.length-1) )
+ {
+ xhtml += DISPLAY_SEPARATOR;
+ }
+ }
+
+ xhtml += DISPLAY_POSTPREND;
+
+ return xhtml;
+}
+
+/**
+ * Return a string containing an XHTML breadcrumb trail based on the
+ * two-dimensional array passed in.
+ */
+function getCrumbTrailXHTML( crumbs )
+{
+ var xhtml = '';
+ xhtml += DISPLAY_PREPREND;
+
+ for( var i = 0; i < crumbs.length; i++ )
+ {
+ xhtml += '';
+ xhtml += sentenceCase( crumbs[i][0] ) + '';
+ if( i != (crumbs.length-1) )
+ {
+ xhtml += '' + DISPLAY_SEPARATOR + '';
+ }
+ }
+
+ xhtml += DISPLAY_POSTPREND;
+ xhtml += '';
+
+ return xhtml;
+}
+
+/* ========================================================================
+ PRINT BREADCRUMB TRAIL
+ ======================================================================== */
+
+// check if we're local; if so, only print the PREPREND_CRUMBS
+if( document.location.href.toLowerCase().indexOf( "http://" ) == -1 )
+{
+ document.write( getCrumbTrail( getBreadcrumbs() ) );
+}
+else
+{
+ document.write( getCrumbTrail( getBreadcrumbs( getDirectoriesInURL() ) ) );
+}
+
diff --git a/proposal/ant-site/anakia/docs/bylaws.html b/proposal/ant-site/anakia/docs/bylaws.html
index 3ddf51aef..de6f67c7b 100644
--- a/proposal/ant-site/anakia/docs/bylaws.html
+++ b/proposal/ant-site/anakia/docs/bylaws.html
@@ -1,99 +1,206 @@
-
-
-
-
-
+
+
-
-
-
-
- Apache Ant - Apache Ant Project Bylaws
-
-
-
-
-
+
+ Apache Ant - Apache Ant Project Bylaws
+
+
+
+
+
This document defines the bylaws under which the Apache Ant project operates.
It defines the the roles and responsibilities of the project, who may vote,
@@ -105,25 +212,15 @@
Incubator project for more information on
how Apache projects operate.
The Project Management Committee (PMC) for Apache Ant was created by a resolution of the
board of the Apache Software Foundation (ASF)on 18th November 2002. The PMC is responsible
@@ -162,17 +259,10 @@
and if supported by 3/4 Majority may recommend a new chair to the board. Ultimately, however, it is
the board's responsibility who to appoint as the PMC chair.
The project's Committers are responsible for the project's technical management. All committers have
write access to the project's source repository. Committers may cast binding votes on any technical
@@ -194,34 +284,20 @@
A committer who makes a sustained contibution to the project will usually be invited to become a member of
the PMC.
All of the volunteers who are contributing time, code, documentation, or resources to the
Ant Project. A developer that makes sustained, welcome contributions to the project for
over six months is usually invited to become a Committer, though the exact timing of
such invitations depends on many factors.
The most important participants in the project are people who use our software. The majority of our
developers start out as users and guide their development efforts from the user's perspective.
@@ -231,28 +307,35 @@
bug reports and feature suggestions. As well, users participate in the Apache community by
helping other users on mailing lists and user support forums.
James Duncan Davidson (duncan at x180.net - http://x180.net/)
@@ -194,28 +289,16 @@ for XML Parsing 1.0 and was the original author of Tomcat and Ant. He
was one of the rabble-rousers within Sun that helped make the Jakarta
Project a reality and served as the first Chairman of the Jakarta PMC.
@@ -315,17 +398,10 @@ implementing the CORBA IDL to C++ 2.0 mapping, skydiving, IDL to Java
compilers, Object Databases (SIGSEV, you da man!) for C++, Java ORB
and EJB runtime environments -- in that order.
-
Simeon H.K. Fitch (simeon.fitch at mseedsoft.com)
@@ -354,28 +430,35 @@ Glenn McAllister is a software developer at SOMA Networks, was formerly
the same at IBM (plus tech writer plus build guy), and does some writing
on the side for the VADD Technical Journal.
Anyone can checkout source code from our anonymous CVS
server. To do so, simply use the following commands (if you are
using a GUI CVS client, configure it appropriatly):
This page lists external resources for Apache Ant: tasks, IDE
integration tools, loggers, you name it. If you've written
something that should be included, please post all relevant
@@ -103,37 +210,27 @@
Nothing listed here is directly supported by the Ant
developers, if you encounter any problems with them, please use
the contact information.
Anteater is a set of Ant tasks for the functional testing of websites
and web services (functional testing being; hit a URL and ensure the
response meets certain criteria). Can test HTTP params, response
@@ -274,13 +357,13 @@
Checkstyle is a development tool to help programmers write
Java code that adheres to a coding standard. Its purpose is to
automate the process of checking Java code, and to spare
@@ -350,13 +426,13 @@
utility.
Clover is an Ant-based Code Coverage tool. It can be used
seamlessly with Ant-based projects. It provides method,
statement, and branch coverage analysis, and has rich
reporting in XML, HTML or via a Swing GUI.
Recursive build support (call ant on every package level,
and only build files in that package or in that package and
everything below) with seperation of source and output.
A little CVS client that can be useful when people are
behind corporate firewall that blocks any cvs
communications. It uses the ViewCVS web interface to access
@@ -648,13 +696,13 @@
Greebo is an Ant-task for downloading dependency files
(currently only jars) from a network to a specified directory,
much like Maven. It supports multiple local and remote
@@ -925,13 +952,13 @@
file.
A task to compile Java sources and manage class file
dependencies. Functionality is equivalent to that of standard
Javac and Depend tasks combined, with improved dependency
checking.
JCSC is a Java Coding Standard Checker which also features
the generation of some code metrics. It is a command line tool
with an Ant task to scan whole package trees. The result can
viewed in an JavaDoc style web page.
Validates XML files against the RELAX NG alternative to XML Schema.
The Jing task for Ant allows you to efficiently validate
multiple files against multiple RELAX NG patterns and integrate
RELAX NG validation with other XML processing.
jMetra is a tool for collecting code metrics across a
project lifecycle and compiling the results into
JavaDoc-styled documentation to analyze project metrics over
@@ -1689,13 +1653,13 @@
Ant tasks.
-
Compatibility:
-
Ant 1.4 and higher
@@ -1703,13 +1667,13 @@
-
URL:
-
@@ -1719,13 +1683,13 @@
-
Contact:
-
@@ -1736,13 +1700,13 @@
-
License:
-
Commercial, free licenses for open source projects and
@@ -1751,17 +1715,10 @@
JRun 4 SP1 ships with lib/jrun-ant-tasks.jar, which defines
three Ant tasks: jrun, jrunapp, and jrunjmx. Documentation
for the tasks can be found in JRun under
@@ -1856,13 +1806,13 @@
existing JRun 4 installation.
A build-time architectural testing tool, designed
to maintain clean layering / tiering / modularity.
Macker works against compiled class files, checking
@@ -1933,13 +1876,13 @@
rules, and Macker keeps you honest about them.
-
Compatibility:
-
Ant 1.5 and higher (1.4 untested but may work)
@@ -1947,13 +1890,13 @@
Purge deletes all but the most recent few files from a fileset.
For example: if you have generated files (logs, .ear, .war, .jar
etc) accumulating in a directory, the purge task will allow you
to delete the older files, keeping just the most recent ones.
SerialVer adds the Java serialver functionality to Apache
Ant. This project adds Tasks and FilterReaders to get, to
insert and to modify the serialVersionUID in the source code
of a serializable class.
The styler task makes useful combinations of XSLT transformations
easy to specify in an Ant build file. Like the built-in Ant task
style, styler can apply a single transformation to a set of XML files.
@@ -2232,13 +2147,13 @@
Tim is a handy utility that can be executed on the command
line or via Ant that automatically formats your import
declarations. Tim is capable of removing unused imports,
@@ -2306,13 +2214,13 @@
pre-determined groups.
Venus Application Publisher's (Vamp) Ant Task Suite allows
you to sign and package your applications into relocatable Web
Archives that you can drop into your web server for
@@ -2452,13 +2346,13 @@
built-in, multi-threaded, ultra light-weight web server.
XDoclet is an extended Javadoc Doclet engine for use in Ant.
It lets you create custom Javadoc @tags and based on those tags
generates source code or other files (such as xml-ish deployment
@@ -2603,13 +2483,13 @@
XmlTask provides a simple means to modify XML documents
without having to learn XSLT. A simple path reference to an
XML node specifies the node you want to change, and how you
@@ -2664,13 +2537,13 @@
perform common XML replacements
yGuard is a free Java(TM) Bytecode Obfuscator Task that
needs no external script or project files. It can completely
be configured and run through the Ant build script. The task
@@ -2741,13 +2607,13 @@
been deployed.
miniRMI is a freeware opensource library that serves as a
lightweight replacement for the original java.rmi packages and
is suitable especially for applets. Ant 1.4+
<rmic> adapter included.
RadPak comes with the (free) HP Bluestone HPAS J2EE server, and is primarily
a GUI tool for packaging and deploying java web and EJB applications
@@ -3263,13 +3070,13 @@
-
Compatibility:
-
bundles Ant 1.3 and docs; adds a jar of extra tasks
@@ -3278,13 +3085,13 @@
The page you are looking it is generated from
this
document. If you want to add a new question, please submit
a patch against this document to one of Ant's mailing lists;
hopefully, the structure is self-explanatory.
-
If you don't know how to create a patch, see the patches
+
If you don't know how to create a patch, see the patches
section of this
page.
-
-
- How do you create the HTML version of this
+
+
+
+
+
+
+
+ How do you create the HTML version of this
FAQ?
-
-
-
-
-
-
We use
+
+
+
+
+
+
We use
Anakia
to render the HTML version from the original XML file.
-
The Velocity stylesheets used to process the XML files can
+
The Velocity stylesheets used to process the XML files can
be found in the xdocs/stylesheets subdirectory of
Ant's CVS repository - the build file docs.xml is
used to drive Anakia. This file assumes that you have the
@@ -403,91 +492,85 @@
well, but if you follow the instruction from Anakia's
homepage, you should get it to work without that. Just make
sure all required jars are in the task's classpath.
According to Ant's original author, James Duncan
Davidson, the name is an acronym for "Another Neat
Tool".
-
Later explanations go along the lines of "ants
+
Later explanations go along the lines of "ants
do an extremely good job at building things", or
"ants are very small and can carry a weight dozens of times
their own" - describing what Ant is intended to
be.
+
+
+ Tell us a little bit about Ant's history.
+
+
+
+
+
+
Initially, Ant was part of the Tomcat code base, when it was
donated to the Apache Software Foundation. It was
created by James Duncan Davidson, who is also the original
author of Tomcat. Ant was there to build Tomcat, nothing
else.
-
Soon thereafter, several open source Java projects realized
+
Soon thereafter, several open source Java projects realized
that Ant could solve the problems they had with Makefiles.
Starting with the projects hosted at Jakarta and the old Java
Apache project, Ant spread like a virus and is now the build
tool of choice for a lot of projects.
-
In January 2000, Ant was moved to a separate CVS module and
+
In January 2000, Ant was moved to a separate CVS module and
was promoted to a project of its own, independent of
Tomcat, and became Apache Ant.
-
The first version of Ant that was exposed to a larger audience
+
The first version of Ant that was exposed to a larger audience
was the one that shipped with Tomcat's 3.1 release on 19 April
2000. This version has later been referred to as Ant
0.3.1.
-
The first official release of Ant as a stand-alone product was
+
The first official release of Ant as a stand-alone product was
Ant 1.1, released on 19 July 2000. The complete release
history:
-
-
- I get checksum errors when I try to extract the
+
+
+
+
+ I get checksum errors when I try to extract the
tar.gz distribution file. Why?
-
-
-
-
-
-
Ant's distribution contains file names that are longer
+
+
+
+
+
+
Ant's distribution contains file names that are longer
than 100 characters, which is not supported by the standard
tar file format. Several different implementations of tar use
different and incompatible ways to work around this
restriction.
-
Ant's <tar> task can create tar archives that use
+
Ant's <tar> task can create tar archives that use
the GNU tar extension, and this has been used when putting
together the distribution. If you are using a different
version of tar (for example, the one shipping with Solaris),
you cannot use it to extract the archive.
-
The solution is to either install GNU tar, which can be
+
The solution is to either install GNU tar, which can be
found here,
or use the zip archive instead (you can extract it using
jar xf).
-
-
- How do I pass parameters from the command line to my
+
+
+
+
+ How do I pass parameters from the command line to my
build file?
-
-
-
-
-
-
Use properties. Using ant
+
+
+
+
+
+
Use properties. Using ant
-Dname=value lets you define values for
properties on the Ant command line. These properties can then be
used within your build file as
any normal property: ${name} will put in
value.
-
-
- How do I redirect standard input or standard output
+
+
+
+
+
+
+
+ How do I redirect standard input or standard output
in the <exec> task?
-
-
-
-
-
-
Say you want to redirect the standard input stream of the
+
+
+
+
+
+
Say you want to redirect the standard input stream of the
cat command to read from a file, something
like:
-
+
@@ -830,8 +903,8 @@ shell-prompt> cat < foo
-
and try to translate it into
-
+
and try to translate it into
+
@@ -855,10 +928,10 @@ shell-prompt> cat < foo
-
This will not do what you expect. The input redirection is
+
This will not do what you expect. The input redirection is
performed by your shell, not the command itself, so this
should read:
-
+
@@ -882,11 +955,11 @@ shell-prompt> cat < foo
-
Note that you must use the value attribute of
+
Note that you must use the value attribute of
<arg> in the last element, in order to have
the command passed as a single, quoted argument. Alternatively,
you can use:
-
+
@@ -909,23 +982,21 @@ shell-prompt> cat < foo
-
Note the double-quotes nested inside the single-quotes.
+
+
+ How do I execute a batch file or shell script from Ant?
+
+
+
+
+
+
On native Unix systems, you should be able to run shell scripts
directly. On systems running a Unix-type shell (for example, Cygwin
on Windows) execute the (command) shell instead - cmd
for batch files, sh for shell scripts - then pass the
@@ -935,7 +1006,7 @@ shell-prompt> cat < foo
the above section
for example <exec> tasks
executing sh. For batch files, use something like:
-
-
- I want to execute a particular target only if
+
+
+
+
+
+
+
+ I want to execute a particular target only if
multiple conditions are true.
-
-
-
-
-
-
There are actually several answers to this question.
-
If you have only one set and one unset property to test,
+
+
+
+
+
+
There are actually several answers to this question.
+
If you have only one set and one unset property to test,
you can specify both an if and an unless
attribute for the target, and they will act as if they
are "anded" together.
-
If you are using a version of Ant 1.3 or earlier, the
+
If you are using a version of Ant 1.3 or earlier, the
way to work with all other cases is to chain targets together
to determine the specific state you want to test for.
-
To see how this works, assume you have three properties:
+
To see how this works, assume you have three properties:
prop1, prop2, and prop3.
You want to test that prop1 and prop2
are set, and that prop3 is not. If the condition
holds true you want to echo "yes".
-
Here is the implementation in Ant 1.3 and earlier:
-
+
Here is the implementation in Ant 1.3 and earlier:
+
@@ -1021,16 +1090,16 @@ shell-prompt> cat < foo
-
Note: <antcall> tasks do not pass
+
Note: <antcall> tasks do not pass
property changes back up to the environment they were called
from, so you would'nt be able to, for example, set a
result property in the cond-if-3 target,
then do
<echo message="result is ${result}"/>
in the cond target.
-
Starting with Ant 1.4, you can use the
+
Starting with Ant 1.4, you can use the
<condition> task.
-
+
@@ -1073,8 +1142,8 @@ shell-prompt> cat < foo
-
This version takes advantage of two things:
-
+
This version takes advantage of two things:
+
If a property a has not been set,
${a} will evaluate to ${a}.
@@ -1082,13 +1151,13 @@ shell-prompt> cat < foo
escape it with another $ - this will also break
the special treatment of the ${ sequence.
-
Because testing for a literal ${property} string
+
Because testing for a literal ${property} string
isn't all that readable or easy to understand,
post-1.4.1 Ant introduces the <isset> element
to the <condition> task.
-
Here is the previous example done using
+
Here is the previous example done using
<isset>:
-
+
@@ -1119,7 +1188,7 @@ shell-prompt> cat < foo
-
The last option is to use a scripting language to set the
+
The last option is to use a scripting language to set the
properties. This can be particularly handy when you need much
finer control than the simple conditions shown here but, of
course, comes with the overhead of adding JAR files to support
@@ -1128,31 +1197,29 @@ shell-prompt> cat < foo
<script> task documentation for more
details.
-
-
- How can I include national characters like German
+
+
+
+
+
+
+
+ How can I include national characters like German
umlauts in my build file?
-
-
-
-
-
-
You need to tell the XML parser which character encoding
+
+
+
+
+
+
You need to tell the XML parser which character encoding
your build file uses, this is done inside the XML
declaration.
-
By default the parser assumes you are using the UTF-8
+
By default the parser assumes you are using the UTF-8
encoding instead of your platform's default. For most Western
European countries you should set the encoding to
ISO-8859-1. To do so, make the very first line
of you build file read like
-
-
- Why does Ant always recompile all my Java files?
-
-
-
-
-
-
In order to find out which files should be compiled, Ant
+
+
+
+
+ Why does Ant always recompile all my Java files?
+
+
+
+
+
+
In order to find out which files should be compiled, Ant
compares the timestamps of the source files to those of the
resulting .class files. Opening all source files
to find out which package they belong to would be very
@@ -1196,45 +1261,43 @@ shell-prompt> cat < foo
source files in a directory hierarchy that mirrors your
package hierarchy and to point Ant to the root of this
directory tree with the srcdir attribute.
-
Say you have <javac srcdir="src"
+
Say you have <javac srcdir="src"
destdir="dest"/>. If Ant finds a file
src/a/b/C.java, it expects it to be in package
a.b so that the resulting .class
file is going to be dest/a/b/C.class.
-
If your source-tree directory structure does not match your
+
If your source-tree directory structure does not match your
package structure, Ant's heuristic won't work, and
it will recompile classes that are up-to-date. Ant is not the
only tool that expects a source-tree layout like this.
-
If you have Java source files that aren't declared to
+
If you have Java source files that aren't declared to
be part of any package, you can still use the <javac>
task to compile these files correctly - just set the
srcdir and destdir attributes to
the actual directory the source
files live in and the directory the class files should go into,
respectively.
+
+
+ I've used a <delete> task to
delete unwanted SourceSafe control files (CVS files, editor
backup files, etc.), but it doesn't seem to work; the files
never get deleted. What's wrong?
-
-
-
-
-
-
This is probably happening because, by default, Ant excludes
+
+
+
+
+
+
This is probably happening because, by default, Ant excludes
SourceSafe control files (vssver.scc) and certain other
files from FileSets.
-
Here's what you probably did:
-
+
Here's what you probably did:
+
@@ -1257,9 +1320,9 @@ shell-prompt> cat < foo
-
You need to switch off the default exclusions,
+
You need to switch off the default exclusions,
and it will work:
-
+
@@ -1283,64 +1346,60 @@ shell-prompt> cat < foo
-
For a complete listing of the patterns that are excluded
+
For a complete listing of the patterns that are excluded
by default, see the user
manual.
-
-
- I have a target I want to skip if a property is set,
+
+
+
+
+
+
+
+ I have a target I want to skip if a property is set,
so I have unless="property" as an attribute
of the target, but all the targets this target
depends on are still executed. Why?
-
-
-
-
-
-
The list of dependencies is generated by Ant before any of the
+
+
+
+
+
+
The list of dependencies is generated by Ant before any of the
targets are run. This allows dependent targets, such as an
init target, to set properties that can control the
execution of the targets higher in the dependency graph. This
is a good thing.
-
However, when your dependencies break down the
+
However, when your dependencies break down the
higher-level task
into several smaller steps, this behaviour becomes
counter-intuitive. There are a couple of solutions available:
-
+
Put the same condition on each of the dependent targets.
Execute the steps using <antcall>,
instead of specifying them inside the depends
attribute.
+
+
+ In my <fileset>, I've put in an
<exclude> of all files followed by an
<include> of just the files I want, but it
isn't giving me any files at all. What's wrong?
-
-
-
-
-
-
The order of the <include> and
+
+
+
+
+
+
The order of the <include> and
<exclude> tags within a <fileset>
is ignored when the FileSet is created. Instead, all of the
<include> elements are processed together,
@@ -1348,103 +1407,95 @@ shell-prompt> cat < foo
elements. This means that the <exclude>
elements only apply to the file list produced by the
<include> elements.
-
To get the files you want, focus on just the
+
To get the files you want, focus on just the
<include> patterns that would be necessary
to get them. If you find you need to trim the list that the
<include> elements produce, then use
<exclude> elements.
-
-
- ant failed to build my program via javac
+
+
+
+
+
+
+
+ ant failed to build my program via javac
even when I put the needed jars in an external
build.properties file and reference them by
pathelement or classpath refid.
-
-
-
-
-
-
When ant loads properties from an external
+
+
+
+
+
+
When ant loads properties from an external
file it dosn't touch the value of properties, trailing blanks
will not be trimmed for example.
-
If the value represents a file path, like a jar needed to
+
If the value represents a file path, like a jar needed to
compile, the task which requires the value, javac for example
would fail to compile since it can't find the file due to
trailing spaces.
-
-
- Ant creates WAR files with a lower-case
+
+
+
+
+
+
+
+ Ant creates WAR files with a lower-case
web-inf or JAR files with a lower-case
meta-inf directory.
-
-
-
-
-
-
No it doesn't.
-
You may have seen these lower-case directory names in
+
+
+
+
+
+
No it doesn't.
+
You may have seen these lower-case directory names in
WinZIP, but WinZIP is trying to be helpful (and fails). If
WinZIP encounters a filename that is all upper-case, it
assumes it has come from an old DOS box andchanges the case to
all lower-case for you.
-
If you extract (or just check) the archive with jar, you
+
If you extract (or just check) the archive with jar, you
will see that the names have the correct case.
+
+
+ Why doesn't (X)Emacs/vi/MacOS X's project builder
correctly parse the error messages generated by Ant?
-
-
-
-
-
-
Ant adds a "banner" with the name of the current
+
+
+
+
+
+
Ant adds a "banner" with the name of the current
task in front of all logging messages - and there are no built-in
regular expressions in your editor that would account for
this.
-
You can disable this banner by invoking Ant with the
+
You can disable this banner by invoking Ant with the
-emacs switch. To make Ant autodetect
Emacs' compile mode, put this into your
.antrc (contributed by Ville Skyttä).
-
+
@@ -1469,10 +1520,10 @@ fi
-
Alternatively, you can add the following snippet to your
+
Alternatively, you can add the following snippet to your
.emacs to make Emacs understand Ant's
output.
-
+
@@ -1500,10 +1551,10 @@ fi
-
Yet another alternative that preserves most of Ant's
+
Yet another alternative that preserves most of Ant's
formatting is to pipe Ant's output through the following Perl
script by Dirk-Willem van Gulik:
For older versions of Ant, you can use a custom
BuildListener that sends out an email
in the buildFinished() method. Will Glozer
<will.glozer@jda.com> has written such a listener based
on JavaMail.
The source is:
-
+
@@ -1839,8 +1884,8 @@ public class BuildMonitor implements BuildListener {
-
-
- How do I get at the properties that Ant was running
+
+
+
+
+
+
+
+ How do I get at the properties that Ant was running
with from inside BuildListener?
-
-
-
-
-
-
You can get at a hashtable with all the properties that Ant
+
+
+
+
+
+
You can get at a hashtable with all the properties that Ant
has been using through the BuildEvent parameter. For
example:
-
+
@@ -1947,31 +1990,29 @@ public void buildFinished(BuildEvent e) {
-
This is more accurate than just reading the same property
+
This is more accurate than just reading the same property
files that your project does, since it will give the correct
results for properties that were specified on the Ant command line.
+
+
+ <chmod> or <exec> doesn't work in Ant
1.3 on Unix
-
-
-
-
-
-
The antRun script in ANT_HOME/bin
+
+
+
+
+
+
The antRun script in ANT_HOME/bin
has DOS instead of Unix line endings; you must remove the
carriage-return characters from this file. This can be done by
using Ant's <fixcrlf> task
or something like:
+
+
+ <style> or <junit> ignores my
<classpath>
-
-
-
-
-
-
These tasks don't ignore your classpath setting, you
+
+
+
+
+
+
These tasks don't ignore your classpath setting, you
are facing a common problem with delegating classloaders.
-
First of all let's state that Ant adds all
+
First of all let's state that Ant adds all
.jar files from ANT_HOME/lib to
CLASSPATH, therefore "in
CLASSPATH" shall mean "either in your
CLASSPATH environment variable or
ANT_HOME/lib" for the rest of this
answer.
-
This question collects a common type of problem: A task
+
This question collects a common type of problem: A task
needs an external library and it has a nested classpath
element so that you can point it to this external library, but
that doesn't work unless you put the external library into the
CLASSPATH.
-
The root of the problem is that the class that needs the
+
The root of the problem is that the class that needs the
external library is on the CLASSPATH.
-
When you specify a nested <classpath> in
+
When you specify a nested <classpath> in
Ant, Ant creates a new class loader that uses the path you
have specified. It then tries to load additional classes from
this classloader.
-
In most cases - for example the two cases above - Ant
+
In most cases - for example the two cases above - Ant
doesn't load the external library directly, it is the loaded
class that does so.
-
In the case of <junit> it is the task
+
In the case of <junit> it is the task
implementation itself and in the case of
<style> it is the implementation of the
org.apache.tools.ant.taskdefs.XSLTLiaison
class.
The ClassLoader class uses a
delegation model to search for classes and resources. Each
instance of ClassLoader has an associated parent
class loader. When called upon to find a class or resource, a
@@ -2070,18 +2107,18 @@ mv /tmp/foo $ANT_HOME/bin/antRun
class loader, does not itself have a parent but may serve as
the parent of a ClassLoader
instance.
-
This means, Ant's class loader will consult the
+
This means, Ant's class loader will consult the
bootstrap class loader first, which tries to load classes from
CLASSPATH. The bootstrap class loader
doesn't know anything about Ant's class loader or
even the path you have specified.
-
If the bootstrap class loader can load the class Ant has
+
If the bootstrap class loader can load the class Ant has
asked it to load, this class will try to load the external
library from CLASSPATH as well - it doesn't
know anything else - and will not find it unless the library
is in CLASSPATH as well.
-
To solve this, you have two major options:
-
+
To solve this, you have two major options:
+
put all external libraries you need in
CLASSPATH as well this is not what you want,
otherwise you wouldn't have found this FAQ entry.
remove the class that loads the external library from
the CLASSPATH.
-
The easiest way to do this is to remove
+
The easiest way to do this is to remove
optional.jar from ANT_HOME/lib. If
you do so, you will have to <taskdef> all
optional tasks and use nested <classpath>
@@ -2100,7 +2137,7 @@ mv /tmp/foo $ANT_HOME/bin/antRun
<classpath> of your
<style> or <junit>
task.
-
If you want to avoid to <taskdef> all
+
If you want to avoid to <taskdef> all
optional tasks you need, the only other option is to remove
the classes that should not be loaded via the bootstrap class
loader from optional.jar and put them into a
@@ -2109,88 +2146,88 @@ mv /tmp/foo $ANT_HOME/bin/antRun
<style> or <junit> task
- and make sure the separate archive is not in
CLASSPATH.
-
In the case of <junit> you'd have
+
In the case of <junit> you'd have
to remove all classes that are in the
org/apache/tools/ant/taskdefs/optional/junit
directory, in the <style> case it is one of
the *Liaison classes in
org/apache/tools/ant/taskdefs/optional.
-
If you use the option to break up optional.jar
+
If you use the option to break up optional.jar
for <junit>, you still have to use a
<taskdef> with a nested
<classpath> to define the junit task.
-
-
- When running Ant 1.4 on Windows XP and JDK 1.4, I get
+
+
+
+
+
+
+
+ When running Ant 1.4 on Windows XP and JDK 1.4, I get
various errors when trying to <exec>, fork
<java> or access environment
variables.
-
-
-
-
-
-
Ant < 1.5 doesn't recognize Windows XP as a flavor
+
+
+
+
+
+
Ant < 1.5 doesn't recognize Windows XP as a flavor
of Windows that runs CMD.EXE instead of
COMMAND.COM. JDK 1.3 will tell Ant that Windows
XP is Windows 2000 so the problem doesn't show up
there.
-
Apart from upgrading to Ant 1.5 or better, setting the
+
Apart from upgrading to Ant 1.5 or better, setting the
environment variable ANT_OPTS to
-Dos.name=Windows_NT prior to invoking Ant has
been confirmed as a workaround.
We are still in the process of defining the guidelines for this
project - to get an idea what they may look like, we want to point
you to the guidelines of the Jakarta
and httpd
projects as well as the work currently on the way at the Incubator project.
Apache Ant is a Java-based build tool. In theory, it is kind of like
Make, but without Make's wrinkles.
@@ -151,17 +253,12 @@ And hey, if you really need to execute a shell command, Ant has an
allows different commands to be executed based on the OS that it is executing
on.
You can view the documentation for the current release (Apache Ant 1.5.1)
online
@@ -169,47 +266,32 @@ You can view the documentation for the current release (Apache Ant 1.5.1)
Comprehensive documentation is included in the source and binary distributions.
Sun, Sun Microsystems, Solaris, Java, JavaServer Web
@@ -107,25 +214,34 @@
Corp. All other product names mentioned herein and throughout
the entire web site are trademarks of their respective
owners.
This list is for developers that are using Ant in their own
projects to ask questions, share knowledge, and discuss issues
related to using Ant as a build tool.
High TrafficSubscribe
@@ -144,28 +239,35 @@
build tool meet and discuss issues, code changes/additions,
etc. Subscribers to this list get notices of each and every
code change, build results, testing notices, etc.
This page details some steps you can take to try and resolve
any problems you may be having with Ant. If you find you can't
@@ -106,14 +213,9 @@
you may encounter - these are just some suggestions to point
you in the right direction.
The first step to take when you have a problem with Ant is to read
the manual entry for the task or
@@ -124,17 +226,10 @@
documentation bug report (see below) to help us improve the Ant
documentation.
If you're still having a problem, the next step is to try and
gather additional information about what Ant is doing.
@@ -150,7 +245,7 @@
This will produce output that starts like the following:
@@ -232,17 +327,10 @@ D:\src\java\Unset.java
generated command line. This can help you to understand whether
you are using the correct attributes and values.
-
-
After examining the debug output, if you still believe that the
problem you are having is caused by Ant, chances are that someone
@@ -263,17 +351,10 @@ D:\src\java\Unset.java
area. However, even this snapshot does not contain every
optional task.
If the current nightly build doesn't resolve your problem, it is
possible that someone else has reported the issue. It is time to
@@ -291,17 +372,10 @@ D:\src\java\Unset.java
add yourself to the CC list to follow the progress
of this bug.
By this time, you may have decided that there is an unreported
bug in Ant. You have a few choices at this point. You can send
@@ -335,17 +409,10 @@ D:\src\java\Unset.java
you receive email asking for further information, please try to
respond, as it will aid in the resolution of your bug.
Sometimes, you may find that Ant just doesn't do what you need it
to. It isn't a bug, as such, since Ant is working the way it is
@@ -363,17 +430,10 @@ D:\src\java\Unset.java
enhancment requests that cover your needs. If so, just add your
vote to these.
If you aren't satisfied with just filing a bug report, you can
try to find the cause of the problem and provide a fix yourself.
@@ -411,28 +471,35 @@ D:\src\java\Unset.java
This makes it easier for developers who need to apply a number
of different patch files.
The Ant-Contrib project is a collection of user supplied
task (like an <if> task) and a development
playground for experimental tasks like a C/C++ compilation
task for different compilers.
AntDoc is a tool that generates HTML documentation from Ant
buildfiles; the generated HTML is inspired from what javadoc
yields. It also offers a simple Ant target launcher named
@@ -189,13 +284,13 @@
via an Ant task, or via a JVM launch.
Anthill is a build tool that promotes a controlled build
process by ensuring that every build reflects the source
repository contents and tagging the repository with a unique
@@ -265,13 +353,13 @@
latest build.
-
Compatibility:
-
bundles Ant 1.3, is compatible with Ant 1.3 to 1.4.1
@@ -279,13 +367,13 @@
CruiseControl is a tool for setting up a continuous build
process. CruiseControl provides an Ant wrapper and a set of
tasks to automate the checkout/build/test cycle. CruiseControl
@@ -339,13 +420,13 @@
the current build, as well as previous build results.
Krysalis Centipede is a project build system based on
Apache Ant. Centipede uses pre-packaged modules called "cents"
that it downloads and installs automatically. Cents can be
@@ -422,13 +496,13 @@
others.
Rant stands for Remote Ant. It is a distributed build
system that allows an Ant build file to launch builds on other
systems and receive exceptions should they occur.
Use the links below to download a source distribution of Ant from
one of our mirrors. You mustverify the integrity of the
@@ -109,17 +215,12 @@ Thus they must be untarred with a GNU compatible version of
You are currently using [preferred]. If you encounter a
problem with this mirror, please select another mirror. If all
mirrors are failing, there are backup mirrors (at the end of
@@ -138,17 +239,12 @@ Other mirrors:
-
Older releases of Ant can be found here. Those
releases are only provided as zip archives that can be
extracted by jar xf archive.zip - we highly
recommend to not use those releases but upgrade to Ant's latest release.
It is essential that you verify the integrity of the downloaded
files using the PGP or MD5 signatures.
The PGP signatures can be verified using PGP or GPG. First
@@ -236,25 +317,34 @@ included in many unix distributions. It is also available as part of
Textutils. Windows users can get binary md5 programs from here, here, or
here.
We highly recommend to verify the PGP signature, though.
- 
