From 8b334fef063f75fd6e64cf5009d530968752f3fd Mon Sep 17 00:00:00 2001 From: Stefan Bodewig Date: Tue, 3 Dec 2002 11:20:23 +0000 Subject: [PATCH] Draft proposal for Ant's standalone website git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@273603 13f79535-47bb-0310-9956-ffa450edef68 --- proposal/ant-site/anakia/.cvsignore | 1 + proposal/ant-site/anakia/build.xml | 64 + proposal/ant-site/anakia/docs/LICENSE | 49 + proposal/ant-site/anakia/docs/ant15_todo.html | 687 ++++ proposal/ant-site/anakia/docs/antnews.html | 379 ++ .../ant-site/anakia/docs/contributors.html | 112 + proposal/ant-site/anakia/docs/cvs.html | 166 + proposal/ant-site/anakia/docs/external.html | 3664 +++++++++++++++++ proposal/ant-site/anakia/docs/faq.html | 2191 ++++++++++ proposal/ant-site/anakia/docs/guidelines.html | 116 + .../anakia/docs/images/ant_logo_large.gif | Bin 0 -> 5360 bytes proposal/ant-site/anakia/docs/index.html | 258 ++ proposal/ant-site/anakia/docs/legal.html | 124 + proposal/ant-site/anakia/docs/mail.html | 164 + proposal/ant-site/anakia/docs/mission.html | 192 + proposal/ant-site/anakia/docs/problems.html | 431 ++ proposal/ant-site/anakia/docs/projects.html | 715 ++++ proposal/ant-site/anakia/docs/resources.html | 1235 ++++++ proposal/ant-site/anakia/xdocs/ant15_todo.xml | 220 + proposal/ant-site/anakia/xdocs/antnews.xml | 185 + .../ant-site/anakia/xdocs/contributors.xml | 12 + proposal/ant-site/anakia/xdocs/cvs.xml | 41 + proposal/ant-site/anakia/xdocs/external.xml | 1357 ++++++ proposal/ant-site/anakia/xdocs/faq.xml | 1175 ++++++ proposal/ant-site/anakia/xdocs/guidelines.xml | 23 + proposal/ant-site/anakia/xdocs/index.xml | 125 + proposal/ant-site/anakia/xdocs/legal.xml | 30 + proposal/ant-site/anakia/xdocs/mail.xml | 57 + proposal/ant-site/anakia/xdocs/mission.xml | 81 + proposal/ant-site/anakia/xdocs/problems.xml | 268 ++ proposal/ant-site/anakia/xdocs/projects.xml | 254 ++ proposal/ant-site/anakia/xdocs/resources.xml | 445 ++ .../ant-site/anakia/xdocs/stylesheets/faq.vsl | 118 + .../anakia/xdocs/stylesheets/project.xml | 44 + .../anakia/xdocs/stylesheets/site.vsl | 81 + .../anakia/xdocs/stylesheets/templates.vm | 186 + .../ant-site/anakia/xdocs/velocity.properties | 2 + 37 files changed, 15252 insertions(+) create mode 100644 proposal/ant-site/anakia/.cvsignore create mode 100644 proposal/ant-site/anakia/build.xml create mode 100644 proposal/ant-site/anakia/docs/LICENSE create mode 100644 proposal/ant-site/anakia/docs/ant15_todo.html create mode 100644 proposal/ant-site/anakia/docs/antnews.html create mode 100644 proposal/ant-site/anakia/docs/contributors.html create mode 100644 proposal/ant-site/anakia/docs/cvs.html create mode 100644 proposal/ant-site/anakia/docs/external.html create mode 100644 proposal/ant-site/anakia/docs/faq.html create mode 100644 proposal/ant-site/anakia/docs/guidelines.html create mode 100644 proposal/ant-site/anakia/docs/images/ant_logo_large.gif create mode 100644 proposal/ant-site/anakia/docs/index.html create mode 100644 proposal/ant-site/anakia/docs/legal.html create mode 100644 proposal/ant-site/anakia/docs/mail.html create mode 100644 proposal/ant-site/anakia/docs/mission.html create mode 100644 proposal/ant-site/anakia/docs/problems.html create mode 100644 proposal/ant-site/anakia/docs/projects.html create mode 100644 proposal/ant-site/anakia/docs/resources.html create mode 100644 proposal/ant-site/anakia/xdocs/ant15_todo.xml create mode 100644 proposal/ant-site/anakia/xdocs/antnews.xml create mode 100644 proposal/ant-site/anakia/xdocs/contributors.xml create mode 100644 proposal/ant-site/anakia/xdocs/cvs.xml create mode 100644 proposal/ant-site/anakia/xdocs/external.xml create mode 100644 proposal/ant-site/anakia/xdocs/faq.xml create mode 100644 proposal/ant-site/anakia/xdocs/guidelines.xml create mode 100644 proposal/ant-site/anakia/xdocs/index.xml create mode 100644 proposal/ant-site/anakia/xdocs/legal.xml create mode 100644 proposal/ant-site/anakia/xdocs/mail.xml create mode 100644 proposal/ant-site/anakia/xdocs/mission.xml create mode 100644 proposal/ant-site/anakia/xdocs/problems.xml create mode 100644 proposal/ant-site/anakia/xdocs/projects.xml create mode 100644 proposal/ant-site/anakia/xdocs/resources.xml create mode 100644 proposal/ant-site/anakia/xdocs/stylesheets/faq.vsl create mode 100644 proposal/ant-site/anakia/xdocs/stylesheets/project.xml create mode 100644 proposal/ant-site/anakia/xdocs/stylesheets/site.vsl create mode 100644 proposal/ant-site/anakia/xdocs/stylesheets/templates.vm create mode 100644 proposal/ant-site/anakia/xdocs/velocity.properties diff --git a/proposal/ant-site/anakia/.cvsignore b/proposal/ant-site/anakia/.cvsignore new file mode 100644 index 000000000..adeec29c3 --- /dev/null +++ b/proposal/ant-site/anakia/.cvsignore @@ -0,0 +1 @@ +velocity.log* diff --git a/proposal/ant-site/anakia/build.xml b/proposal/ant-site/anakia/build.xml new file mode 100644 index 000000000..d879e555a --- /dev/null +++ b/proposal/ant-site/anakia/build.xml @@ -0,0 +1,64 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + AnakiaTask is not present! Please check to make sure that + velocity.jar is in your classpath. + + + + + + + + + + + + + + + + + + + + + + + diff --git a/proposal/ant-site/anakia/docs/LICENSE b/proposal/ant-site/anakia/docs/LICENSE new file mode 100644 index 000000000..b279c7a20 --- /dev/null +++ b/proposal/ant-site/anakia/docs/LICENSE @@ -0,0 +1,49 @@ +/* + * ============================================================================ + * The Apache Software License, Version 1.1 + * ============================================================================ + * + * Copyright (C) 2000-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 "Ant" 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 . + * + */ diff --git a/proposal/ant-site/anakia/docs/ant15_todo.html b/proposal/ant-site/anakia/docs/ant15_todo.html new file mode 100644 index 000000000..d1ab8ddab --- /dev/null +++ b/proposal/ant-site/anakia/docs/ant15_todo.html @@ -0,0 +1,687 @@ + + + + + + + + + + + + + + + Apache Ant - Ant 1.5 Release To-Do List + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Ant 1.5 Release To-Do List + +
+
+ + + +
+ + Open + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + Item + + + + Details + + + + Assigned + +
+ + Bugzilla bugs under 30 + + + + or at least address most of them in some way + + + + All Committers + +
+ + Document Path datatype + + + + It's documented, but more hidden than the other types + + + + Erik + +
+ + Novell NetWare support + + + +   + + + + Jeff Tulley + +
+ + XMLCatalog more integrated + + + + Several tasks could still use XMLCatalog integration + + + +   + +
+ + Make default excludes customizable + + + + With the setting of an ant.default.excludes property? + + + + Erik + +
+ + Fully functional on Java 1.4 + + + + Fix outstanding java1.4 defects, maybe add an + assertions datatype for java and other tasks (junit?) + which lets people turn on asserts. + + + + + Steve + any other help he can get + +
+
+
+ + + +
+ + Done + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + Item + + + + Details + + + + Assigned + +
+ + Selectors + + + +   + + + + Bruce + +
+ + Extension utilities + + + + Port across task that prints out details of extensions for + a certain library/jar, or all jars in a path. Port across task + that generates a manifest (including dependencies and extension + specification) based on a set of jars in path. Port across task + that checks that the list of pre-req extensions are present in + path. + + + + Peter + +
+ + XmlLogger implements BuildLogger + + + + Its currently a BuildListener, lets remove the confusion + + + + Erik + +
+ + Dotnet library tweaks + + + + update to release, add uptodateness, add a web service + import (for Axis interop testing) + + + + Steve, in a really long meeting + +
+ + compiler attribute for rmic + + + +   + + + + Stefan + +
+ + PGP signing task if possible + + + + Not done, but deemed impossible - at least in the 1.5 + time frame. + + + + Stefan + +
+ + JUnit's System.err/.out handling + + + + showoutput attribute has been added - doesn't work in + some cases yet (same reason as bug PR 7980) + + + + Stefan + +
+ + Base compiler command line switches on the selected + compiler, not the current JDK + + + +   + + + + Stefan + +
+ + <input> + + + +   + + + + Stefan + +
+ + Make javadoc a real directory based task + + + +   + + + + Stefan + +
+
+
+ + + +
+ + Bug Reports Short-Cuts + +
+
+

Note: You can sort the report results by clicking on the column-headings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + New|Assigned|Reopened Bug Reports: + +
+ + All + + +
+ + - minus Enhancements + + +
+ + New|Assigned|Reopened Bug Reports by Component: + +
+ + Build Process + + +
+ + - minus Enhancements + + +
+ + Core + + +
+ + - minus Enhancements + + +
+ + Core Tasks + + +
+ + - minus Enhancements + + +
+ + Documentation + + +
+ + - minus Enhancements + + +
+ + Optional Tasks + + +
+ + - minus Enhancements + + +
+ + Other + + +
+ + - minus Enhancements + + +
+ + Wrapper Scripts + + +
+ + - minus Enhancements + + +
+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/antnews.html b/proposal/ant-site/anakia/docs/antnews.html new file mode 100644 index 000000000..0800f068b --- /dev/null +++ b/proposal/ant-site/anakia/docs/antnews.html @@ -0,0 +1,379 @@ + + + + + + + + + + + + + + + + + + + Apache Ant - Ant News + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Ant 1.5.1 + +
+
+

October 3, 2002 - Ant 1.5.1 Available !

+

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. +

+
+
+ + + +
+ + Ant 1.5.1Beta1 + +
+
+

August 19, 2002 - Ant 1.5.1 Beta1 Available !

+

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. +

+
+
+ + + +
+ + Ant 1.5 + +
+
+

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.

+

July 10, 2002 - Ant 1.5 Released!

+

The final version of Ant 1.5 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. +

+
+
+ + + +
+ + Ant 1.5Beta3 + +
+
+

June 24, 2002 - Ant 1.5 Beta3 Available!

+

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. +

+
+
+ + + +
+ + Ant 1.5Beta2 + +
+
+

June 1, 2002 - Ant 1.5 Beta2 Available!

+

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. +

+
+
+ + + +
+ + Ant 1.5Beta1 + +
+
+

Ant 1.5 Beta1 Available !

+

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. +

+
+
+ + + +
+ + Ant wins again! + +
+
+

Apr 29, 2002: Ant wins Software Development magazine's + 2002 Productivity Award.

+

+ + Ant has been awarded a 2002 Productivity Award by + Software Development + magazine. Read the + + press release for more information and the full list of winners. +

+
+
+ + + +
+ + Ant has won! + +
+
+

Mar 26, 2002: Ant wins the JavaWorld Editors' Choice + Award

+

+ + Ant has won the JavaWorld Editors' Choice Award for + Most Useful Java Community-Developed Technology. + Read the + full article -- or jump directly to the bit about + our award :)

+
+
+ + + +
+ + Java 1.4 Support + +
+
+

Feb 15, 2002: Java 1.4 Support

+

+ Java 1.4 has now been released by Sun. The latest Ant source supports + the new assert statement in the compiler task via the source + attribute. It also contains a compatibility fix needed for some ant tasks + 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. +

+
+
+ + + +
+ + See our new logo! + +
+
+

Have a look at our new cool logo!

+
+
+ + + +
+ + Ant 1.4.1 + +
+
+

11 October 2001 Ant 1.4.1 released !

+

Please visit the + + download area. +

+
+
+ + + +
+ + Ant 2.0 Requirements Collected - Next is Design + +
+
+

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 + give you an idea of what Ant2 is going to look like.

+

Several details can only be decided in the light of real code + 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.

+
+
+ + + +
+ + Best-Practices Profile of Ant at Sun's Dot-Com Builder + +
+
+

Sun has released an introductory article on Ant on their + Dot-Com Builder site on May 30 2001. See http://dcb.sun.com/practices/profiles/ant.jsp

+
+
+ + + +
+ + Ant 2.0 Requirements + +
+
+

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 + be addressed. +

+

+ As we continue to evolve and enhance Ant 1.x, it is now time to define what Ant 2.0 will + encompass. Ant 2.0 will be a major rearchitecting of Ant. It has a number of goals including: +

    +
  • Define the "contract" with build file writers to which Ant will be bound.
    • +
  • Define the "contract" between the Ant core and Task writers.
    • +
  • Make Ant more easily extendable by allowing additional tasks to be "dropped" in.
    • +
  • Allow Ant to function as a component to simplify integration with GUIs and IDEs.
    • +
  • Make Ant more regular and logical.
    • +
+ + It is expected that Ant 2.0 will break Ant 1.x based build files. The intention is to + make this the last time that will happen. +

+

+ To advance the definition of Ant, user requirements are now being accepted on the + Ant-Dev mailing list. Any requirement will be accepted for consideration. The + requirements are being collected into a document which is available + on-line. New features will be excepted + until March 21st, 2001. At that time, each requirement will be discussed + for inclusion in an Ant 2.0 requirement document. +

+

+ For your reference some of the goals which have shaped the development of Ant 1.x are + available here. These continue to be + relevant to Ant 2.0. +

+

+ If you want to shape the future of Ant, join the + Ant-Dev mailing list and contribute + your ideas. +

+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/contributors.html b/proposal/ant-site/anakia/docs/contributors.html new file mode 100644 index 000000000..e2b993598 --- /dev/null +++ b/proposal/ant-site/anakia/docs/contributors.html @@ -0,0 +1,112 @@ + + + + + + + + + + + + + Apache Ant - Contributors + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Contributors + +
+
+

Copy info from Jakarta here - add new stuff.

+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/cvs.html b/proposal/ant-site/anakia/docs/cvs.html new file mode 100644 index 000000000..9f3447f86 --- /dev/null +++ b/proposal/ant-site/anakia/docs/cvs.html @@ -0,0 +1,166 @@ + + + + + + + + + + + + + Apache Ant - CVS Repository + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Access the Source Tree (AnonCVS) + +
+
+

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):

+
+ + + + + + + + + + + + + + + + + 
+cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
+password: anoncvs
+
+
+ + + + + + + + + + + + + + + + + 
+cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout [module-name]
+
+

Modules available for access are (click the links to view the + CVS tree via ViewCVS):

+ +

If you are not familiar with CVS, Jakarta's + CVS page may hold many helpful hints.

+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/external.html b/proposal/ant-site/anakia/docs/external.html new file mode 100644 index 000000000..72b96915e --- /dev/null +++ b/proposal/ant-site/anakia/docs/external.html @@ -0,0 +1,3664 @@ + + + + + + + + + + + + + + + Apache Ant - External Tools and Tasks + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + External Tools and Tasks + +
+
+

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 + information to one of the mailing lists.

+

Nothing listed here is directly supported by the Ant + developers, if you encounter any problems with them, please use + the contact information.

+
+
+ + + +
+ + Tasks + +
+
+ + + +
+ + AJC + +
+
+

AspectJ is an + aspect-oriented extension to Java. This task compiles a + source tree using the AspectJ compiler -- AJC.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 + +
+ + URL: + + + + http://aspectj.org/dl + +
+ + Contact: + + + + support@aspectj.org + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Anakia + +
+
+

Actually, Anakia is more than just an Ant task, it is a an + XML transformation tool based on JDOM, Velocity and Ant.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and later + +
+ + URL: + + + + http://jakarta.apache.org/velocity/anakia.html + +
+ + Contact: + + + + Velocity mailing lists + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Anteater + +
+
+

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 + codes, XPath, regexp and Relax NG expressions. Includes HTML reporting + (based on junitreport) and a hierarchical grouping system for quickly + configuring large test scripts. +

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5 and later + +
+ + URL: + + + + http://aft.sourceforge.net + +
+ + Contact: + + + + developer + mailing list + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Checkstyle + +
+
+

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 + humans of this boring (but important) task.

+

Checkstyle can be run via an Ant task or a command line + utility.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 to 1.4.1 + +
+ + URL: + + + + http://checkstyle.sourceforge.net/ + +
+ + Contact: + + + + Oliver Burn + +
+ + License: + + + + Starting with release 2.0 the license is the GNU + Lesser General Public License. Prior releases were under + the GNU General Public License. + +
+
+
+ + + +
+ + CleanImports + +
+
+

Removes unneeded imports. Formats your import + sections. Flags ambiguous imports.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 + +
+ + URL: + + + + http://www.euronet.nl/users/tomb/cleanImports/index.html + +
+ + Contact: + + + + Tom Brus + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Clover + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4.1 or greater + +
+ + URL: + + + + http://www.thecortex.net/clover + +
+ + Contact: + + + + clover-support@cortexebusiness.com.au + +
+ + License: + + + + Commercial, free licenses available for open source + projects. + +
+
+
+ + + +
+ + Configure + +
+
+

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.

+

The task generates build files in any subdirectory (except + for CVS-directories) for you. Only place one build.xml file in + the top and call target 'setup' or + 'rescan'.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and 1.3 + +
+ + URL: + + + + http://www.dsdelft.nl/~lemval/ant/ + +
+ + Contact: + + + + M.J.P. van Leeuwen + +
+ + License: + + + + License derived from Apache Software License + +
+
+
+ + + +
+ + CVSGrab + +
+
+

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 + the CVS repository via standard http, and downloads all the + files present in it.

+

It works from the command line or as an Ant task.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 or higher + +
+ + URL: + + + + http://cvsgrab.sourceforge.net/ + +
+ + Contact: + + + + CVSGrab + user mailing list + +
+ + License: + + + + LGPL + +
+
+
+ + + +
+ + Doxygen task + +
+
+

There are two Ant tasks for running the Doxygen + documentation system.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.1 and later + +
+ + URL: + + + + http://www.bgw.org/projects/java/ant/ + +
+ + Contact: + + + + Kyle R. Burton + +
+ + License: + + + + Apache Software Foundation License + +
+

and

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5 and later + +
+ + URL: + + + + http://ant-doxygen.sourceforge.net + +
+ + Contact: + + + + Karthik A Kumar + +
+ + License: + + + + Apache Software Foundation License + +
+
+
+ + + +
+ + GenJar + +
+
+

Builds a JAR file based on class dependencies rather than simply the contents of a directory

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 alpha (built after 2001/08/04) and later + +
+ + URL: + + + + http://genjar.sourceforge.net/ + +
+ + Contact: + + + + Jesse Stockall + +
+ + License: + + + + Apache Software Foundation License + +
+
+
+ + + +
+ + Greebo + +
+
+

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 + repositories with either flat or maven-like structures. It can + read the dependency list from a Maven project file, a + maven-like dependency file, or directly from the build.xml + file.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5 + +
+ + URL: + + + + http://www.discore.com/oz/new/index.htm + +
+ + Contact: + + + + Ozben Evren + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Importscrubber + +
+
+

Removes unnecessary import statements from a Java source code file.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 + +
+ + URL: + + + + http://importscrubber.sourceforge.net/ + +
+ + Contact: + + + + Tom Copeland + +
+ + License: + + + + LGPL + +
+
+
+ + + +
+ + IsDirValidator + +
+
+

Checks whether a given directory structure conforms to + certain rules that are defined via nested elements of the + task.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://isvalidator.sourceforge.net/en/isDirValidator.htm + +
+ + Contact: + + + + Iñigo Serrano + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + Jalopy + +
+
+

An Ant Plug-in for the Java Source Code Formatter + Jalopy.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 (or higher) + +
+ + URL: + + + + http://jalopy.sourceforge.net + +
+ + Contact: + + + + http://jalopy.sf.net/contact.html + +
+ + License: + + + + Starting with release 1.0 Beta 6 the license is the + BSD License. Prior releases were under the GNU General + Public License. + +
+
+
+ + + +
+ + Javamake + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4.1 + +
+ + URL: + + + + http://www.experimentalstuff.com/Technologies/JavaMake/index.html + +
+ + Contact: + + + + Mikhail Dmitriev + +
+ + License: + + + + BSD-like License + +
+
+
+ + + +
+ + J2ME Ant Tasks + +
+
+

There are three different sets of tasks to help build Java 2 Platform, Micro + Edition (J2ME) applications.

+

This set supports CLDC and the K Virtual Machine (KVM):

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 + +
+ + URL: + + + + http://www.dribin.org/dave/j2me_ant/ + +
+ + Contact: + + + + Dave Dribin + +
+ + License: + + + + Apache Software License + +
+

And this set works with the J2ME Wireless Toolkit and MIDP + for PalmOS:

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 + +
+ + URL: + + + + http://www.stampysoft.com/ant/ + +
+ + Contact: + + + + Josh Eckels + +
+ + License: + + + + MIT License + +
+

With Antenna, you can compile, preverify, package, and + obfuscate your MIDP applications, as well as convert them to + PRC files designed to run on MIDP for PalmOS. The tasks are + mostly built around the Wireless Toolkit and the free + RetroGuard obfuscator, with some additional gimmicks like + automatic version numbering.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4.1 or later + +
+ + URL: + + + + http://antenna.sourceforge.net/ + +
+ + Contact: + + + + Jörg Pleumann + +
+ + License: + + + + GNU Lesser General Public License + +
+
+
+ + + +
+ + javarec + +
+
+

Ant tasks that generate record classes for VisualAge for + Java from Cobol copy books.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://glezen.org/javarec/ + +
+ + Contact: + + + + Paul Glezen + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + JCSC + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant >= 1.5 + +
+ + URL: + + + + http://jcsc.sourceforge.net/ + +
+ + Contact: + + + + Ralph Jocham + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + Jing Task + +
+
+

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.

+ + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 and later + +
+ + URL: + + + + + http://www.thaiopensource.com/relaxng/jing-ant.html + +
+ + License: + + + + BSD-like + +
+
+
+ + + +
+ + jMetra + +
+
+

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 + time. jMetra is best utilized by integrating it with your + project's scheduled build process.

+

It works from the command line or using several provided + Ant tasks.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 and higher + +
+ + URL: + + + + + http://www.jmetra.com/ + + +
+ + Contact: + + + + + R Todd Newton + + + +
+ + License: + + + + Commercial, free licenses for open source projects and + evaluations. + +
+
+
+ + + +
+ + JNI + +
+
+

+ + JNI is a free toolkit that makes easy work of + integrating Java and C through the Java Native + Interface (JNI). It includes a code generator that + generates both Java "proxy" classes to access C + "peer" classes, and C "proxy" classes to access + Java "peer" classes or interfaces. It also + includes a core library with a simplified JVM + interface as well as "helper" classes to ease + working with the JNI data types. The code + generation is driven by an XML project file that + can be created with the assistance of the GUI + Project Manager. The code generation can be + invoked either from Ant or from the + GUI. Includes a comprehensive printable PDF User + Guide and plenty of examples.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://jnipp.sf.net/ + +
+ + Contact: + + + + Phillip E. Trewhella + +
+ + License: + + + + GNU LGPL + +
+
+
+ + + +
+ + JRun Ant Tasks + +
+
+

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 + docs/ant/jrun.html.

+

Note that the service pack must be installed on top of an + existing JRun 4 installation.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 or higher + +
+ + URL: + + + + http://dynamic.macromedia.com/bin/MM/software/trial/hwswrec.jsp?product=jrun_sp + +
+ + Contact: + + + + Brian Deitte + +
+ + License: + + + + Commercial + +
+
+
+ + + +
+ + Macker + +
+
+

A build-time architectural testing tool, designed + to maintain clean layering / tiering / modularity. + Macker works against compiled class files, checking + dependencies between classes against a set of + pattern-based access rules you specify for your + project in an XML rules file. Macker doesn't presume + anything about your architecture -- you write the + rules, and Macker keeps you honest about them.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5 and higher (1.4 untested but may work) + +
+ + URL: + + + + http://innig.net/macker/ + +
+ + Contact: + + + + Paul Cantrell + +
+ + License: + + + + GNU GPL 2.0 + +
+
+
+ + + +
+ + PMD + +
+
+

PMD checks Java source code for unused variables, + unnecessary object creation, etc

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 and higher + +
+ + URL: + + + + http://pmd.sf.net/ + +
+ + Contact: + + + + Tom Copeland + +
+ + License: + + + + Apache Software Foundation License + +
+
+
+ + + +
+ + Purge + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 or above + +
+ + URL: + + + + http://www.dallaway.com/ant/ + +
+ + Contact: + + + + Richard Dallaway + +
+ + License: + + + + LGPL + +
+
+
+ + + +
+ + SerialVer + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5.1 and later + +
+ + URL: + + + + http://serialver.sourceforge.net/ + +
+ + Contact: + + + + developer mailing list + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + Styler + +
+
+

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. + But it can also:

+
    +
  • handle multiple transformations, in parallel or pipelined.
    • +
  • enable transformations that split or merge files
    • +
  • process non-XML files, especially HTML (based on JTidy)
    • +
  • apply non-XSLT transformation, especially "regular + fragmentations"
    • +
  • use any custom XMLReader or XMLFilter class to handle new file + formats and transformation techniques.
    • +
+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://www.langdale.com.au/styler/ + +
+ + Contact: + + + + Arnold deVos + +
+ + License: + + + + LGPL + +
+
+
+ + + +
+ + Tidy Imports (Tim) + +
+
+

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, + expanding or collapsing imports and even organising them into + pre-determined groups.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 and later + +
+ + URL: + + + + http://www.chive.com/tim.htm + +
+ + Contact: + + + + support@chive.com + +
+ + License: + + + + Commercial + +
+
+
+ + + +
+ + TiniAnt + +
+
+

TiniAnt is an Ant task to support building applications for + the TINI.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 to 1.4.1 + +
+ + URL: + + + + http://tiniant.sourceforge.net/ + +
+ + Contact: + + + + Sean Kelly + +
+ + License: + + + + BSD-like license + +
+
+
+ + + +
+ + Venus Application Publisher's (Vamp) Ant Task Suite + +
+
+

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 + single-click launching using Java Web Start or into single + Java Archive installers that serve up their content through a + built-in, multi-threaded, ultra light-weight web server.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and 1.3 + +
+ + URL: + + + + http://www.geocities.com/vamp201/ant.html + +
+ + Contact: + + + + Gerald Bauer + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + WOProject + +
+
+

WOProject provides a set of tools to work with + WebObjects 5.1 + independent from platform and IDE. It significantly + improves developer productivity + and makes complex project structures more flexible compared to + traditional Makefile-based approach. +

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://objectstyle.org/woproject/ + +
+ + Contact: + + + + Andrus Adamchik + +
+ + License: + + + + Apache license + +
+
+
+ + + +
+ + XDoclet + +
+
+

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 + descriptors). Templates and matching tasks are provided to generate + EJB and web application deployment descriptors. +

+ + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://sourceforge.net/projects/xdoclet/ + +
+ + License: + + + + BSD license + +
+
+
+ + + +
+ + XmlTask + +
+
+

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 + want to allow XML insertion and removal, or attribute + changes. The emphasis is on providing the simplest means to + perform common XML replacements

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 and later + +
+ + URL: + + + + http://www.oopsconsultancy.com/software/xmltask.html + +
+ + Contact: + + + + xmltask@oopsconsultancy.com + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + yGuard + +
+
+

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 + supports multiple Jar files at once and makes use of + patternsets and regular expressions to specify elements, which + should be left unobfuscated. Additionally it can be used to + produce patches for obfuscated applications that have already + been deployed.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5 and later + +
+ + URL: + + + + http://www.yworks.com/products/yguard + +
+ + Contact: + + + + yGuard@yWorks.com + +
+ + License: + + + + Library: LGPL, Task: Commercial + +
+
+
+
+
+ + + +
+ + Compiler Implementations + +
+
+ + + +
+ + miniRMI <rmic> implementation + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 and later + +
+ + URL: + + + + http://dione.zcu.cz/~toman40/miniRMI/ + +
+ + Contact: + + + + Petr Toman + +
+ + License: + + + + Gnu Lesser Public License + +
+
+
+
+
+ + + +
+ + IDE and Editor Integration + +
+
+ + + +
+ + AntFarm + +
+
+

A plugin that integrates Ant into the jEdit editor.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.3 + +
+ + URL: + + + + http://plugins.jedit.org/plugins/AntFarm + +
+ + Contact: + + + + jEdit developers mailinglist + +
+ + License: + + + + Apache Software License + +
+
+
+ + + +
+ + AntMan + +
+
+

An AddIn that integrates Ant with the JDeveloper IDE

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4.1 + +
+ + URL: + + + + http://www.erudra.com/antman/index.html + +
+ + Contact: + + + + Ashok Sridhar + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + AntRunner + +
+
+

An OpenTool that integrates Ant into the JBuilder IDE.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and 1.3 + +
+ + URL: + + + + http://www.dieter-bogdoll.de/java/AntRunner/ + +
+ + Contact: + + + + Dieter Bogdoll + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + AntWork + +
+
+

A plugin that integrates Ant into the Jext editor.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and 1.3 + +
+ + URL: + + + + ftp://jext.sourceforge.net/pub/jext/plugins/AntWork.zip + +
+ + Contact: + + + + Klaus Hartlage + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + Eclipse + +
+
+

Eclipse is a universal tool platform with Ant integration.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.3 - 1.4.1 + +
+ + URL: + + + + http://www.eclipse.org + +
+ + Contact: + + + + news://news.eclipse.org/eclipse.tools + +
+ + License: + + + + Common Public License Version 1.0 + +
+
+
+ + + +
+ + HP RadPak + +
+
+

+ 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 + as WAR and EAR files. The tool is ant based, and can be used with + as a GUI for general ant development, providing form based entry + of task attributes, and an animated display of task + execution. +

+ + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.3 and docs; adds a jar of extra tasks + to any existing ant installation under ANT_HOME + +
+ + URL: + + + + http://www.bluestone.com/products/hp-as/ + +
+ + License: + + + + Proprietary but free to download + +
+
+
+ + + +
+ + IntelliJ IDEA 2.0 + +
+
+

Java IDE with refactoring support and Ant integration.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.3 + +
+ + URL: + + + + http://www.intellij.com/idea/ + +
+ + Contact: + + + + support@intellij.com + +
+ + License: + + + + Commercial + +
+
+
+ + + +
+ + JDE(E) 2.2.8 + +
+
+

The Java Development Environment for Emacs (JDEE) supports + Apache Ant as one of three built-in ways to build your + applications.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and later + +
+ + URL: + + + + http://jde.sunsite.dk/ + +
+ + Contact: + + + + JDEE Mailing list. + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + NetBeans / Sun ONE Studio + +
+
+

A module that integrates Ant into the NetBeans or Sun ONE Studio (formerly Forte for Java) IDEs.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.4.1 + +
+ + URL: + + + + http://ant.netbeans.org/ + +
+ + Contact: + + + + nbdev@netbeans.org + +
+ + License: + + + + Sun Public License + +
+
+
+ + + +
+ + Oracle9i JDeveloper + +
+
+

Java IDE with support for Ant.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.5.1 + +
+ + URL: + + + + http://otn.oracle.com/products/jdev/ + +
+ + Contact: + + + + jdeveloperbeta_us@oracle.com + +
+ + License: + + + + Commercial + +
+
+
+ + + +
+ + WebSphere Studio Application Developer + +
+
+

WSAD features Ant integrate by virtue of being built on the Eclipse tools platform.

+ + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.4.1 + +
+ + Article: + + + + Ant Integration Part1 + +
+ + License: + + + + Commercial + +
+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/faq.html b/proposal/ant-site/anakia/docs/faq.html new file mode 100644 index 000000000..d54971906 --- /dev/null +++ b/proposal/ant-site/anakia/docs/faq.html @@ -0,0 +1,2191 @@ + + + + + + + + + + + + + + + Apache Ant - Frequently Asked Questions + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Questions + +
+
+ + + +
+ + About this FAQ + +
+
+ +
+
+ + + +
+ + General + +
+
+ +
+
+ + + +
+ + Installation + +
+
+ +
+
+ + + +
+ + How do I ... + +
+
+ +
+
+ + + +
+ + It doesn't work (as expected) + +
+
+ +
+
+ + + +
+ + Ant and IDEs/Editors + +
+
+ +
+
+ + + +
+ + Advanced Issues + +
+
+ +
+
+ + + +
+ + Known Problems + +
+
+ +
+
+
+
+ + + + +
+ + Answers + +
+
+ + + + +
+ + + Where do I find the latest version of this + document? + + +
+
+

The latest version can always be found at Ant's homepage + http://jakarta.apache.org/ant/faq.html.

+
+
+ + + + + +
+ + + How can I contribute to this FAQ? + + +
+
+

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 + section of this + page.

+
+
+ + + + + +
+ + + How do you create the HTML version of this + FAQ? + + +
+
+

We use + Anakia + to render the HTML version from the original XML file.

+

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 + jakarta-site2 module checked out from CVS as + 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.

+
+
+ + + + + +
+ + + What is Apache Ant? + + +
+
+

Ant is a Java-based build tool. In theory, it is kind of + like Make, without Make's wrinkles and with the full + portability of pure Java code.

+
+
+ + + + + +
+ + + Why do you call it Ant? + + +
+
+

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 + 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 + 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 + 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 + 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 + Ant 1.1, released on 19 July 2000. The complete release + history:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + Ant Version + + + + Release Date + +
+ + 1.1 + + + + 19 July 2000 + +
+ + 1.2 + + + + 24 October 2000 + +
+ + 1.3 + + + + 3 March 2001 + +
+ + 1.4 + + + + 3 September 2001 + +
+ + 1.4.1 + + + + 11 October 2001 + +
+ + 1.5 + + + + 10 July 2002 + +
+ + 1.5.1 + + + + 3 October 2002 + +
+
+
+ + + + + +
+ + + I get checksum errors when I try to extract the + tar.gz distribution file. Why? + + +
+
+

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 + 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 + 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 + build file? + + +
+
+

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 can I use Jikes-specific command-line + switches? + + +
+
+

A couple of switches are supported via "magic" + properties:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + switch + + + + property + + + + default + +
+ + +E + + + + build.compiler.emacs + + + + false == not set + +
+ + +P + + + + build.compiler.pedantic + + + + false == not set + +
+ + +F + + + + build.compiler.fulldepend + + + + false == not set + +
+ + (Only for Ant < 1.4; replaced by the + nowarn + attribute of the <javac> + task after that.)
-nowarn + + 		+ + build.compiler.warnings + + + + true == not set + +
+

With Ant >= 1.5, you can also use nested + <compilerarg> elements with the + <javac> task.

+
+
+ + + + + +
+ + + How do I include a < character in my command-line arguments? + + +
+
+

The short answer is "Use: &lt;".

+

The long answer is that this probably won't do what you + want anyway (see the next + section).

+
+
+ + + + + +
+ + + How do I redirect standard input or standard output + in the <exec> task? + + +
+
+

Say you want to redirect the standard input stream of the + cat command to read from a file, something + like:

+
+ + + + + + + + + + + + + + + + + 
+shell-prompt> cat < foo
+
+
+

and try to translate it into

+
+ + + + + + + + + + + + + + + + + 
+<exec executable="cat">
+  <arg value="&lt;" />
+  <arg value="foo" />
+</exec>
+
+
+

This will not do what you expect. The input redirection is + performed by your shell, not the command itself, so this + should read:

+
+ + + + + + + + + + + + + + + + + 
+<exec executable="/bin/sh">
+  <arg value="-c" />
+  <arg value="cat &lt; foo" />
+</exec>
+
+
+

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:

+
+ + + + + + + + + + + + + + + + + 
+<exec executable="/bin/sh">
+  <arg line='-c "cat &lt; foo"'/>
+</exec>
+
+
+

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 + batch file or shell script (plus any arguments to the script) + as a single command, using the /c or + -c switch, respectively. See + the above section + for example <exec> tasks + executing sh. For batch files, use something like:

+
+ + + + + + + + + + + + + + + + + 
+<exec dir="." executable="cmd" os="Windows NT">
+  <arg line="/c test.bat"/>
+</exec>
+
+
+
+
+ + + + + +
+ + + 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, + 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 + 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: + 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:

+
+ + + + + + + + + + + + + + + + + 
+<target name="cond" depends="cond-if"/>
+
+<target name="cond-if" if="prop1">
+  <antcall target="cond-if-2"/>
+</target>
+
+<target name="cond-if-2" if="prop2">
+  <antcall target="cond-if-3"/>
+</target>
+
+<target name="cond-if-3" unless="prop3">
+  <echo message="yes"/>
+</target>
+
+
+

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 + <condition> task.

+
+ + + + + + + + + + + + + + + + + 
+<target name="cond" depends="cond-if,cond-else"/>
+
+<target name="check-cond">
+  <condition property="cond-is-true">
+    <and>
+      <not>
+        <equals arg1="${prop1}" arg2="$${prop1}" />
+      </not>
+      <not>
+        <equals arg1="${prop2}" arg2="$${prop2}" />
+      </not>
+      <equals arg1="${prop3}" arg2="$${prop3}" />
+    </and>
+  </condition>
+</target>
+
+<target name="cond-if" depends="check-cond" if="cond-is-true">
+  <echo message="yes"/>
+</target>
+
+<target name="cond-else" depends="check-cond" unless="cond-is-true">
+  <echo message="no"/>
+</target>
+
+
+

This version takes advantage of two things:

+
    +
  • If a property a has not been set, + ${a} will evaluate to ${a}.
    • + +
  • To get a literal $ in Ant, you have to + escape it with another $ - this will also break + the special treatment of the ${ sequence.
    • +
+

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 + <isset>:

+
+ + + + + + + + + + + + + + + + + 
+<target name="check-cond">
+  <condition property="cond-is-true">
+    <and>
+      <isset property="prop1"/>
+      <isset property="prop2"/>
+      <not>
+        <isset property="prop3"/>
+      </not>
+    </and>
+  </condition>
+</target>
+
+
+

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 + the language, to say nothing of the added maintenance in requiring + two languages to implement a single system. See the + + <script> task documentation for more + details.

+
+
+ + + + + +
+ + + How can I include national characters like German + umlauts in my build file? + + +
+
+

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 + 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

+
+ + + + + + + + + + + + + + + + + 
+<?xml version="1.0" encoding="ISO-8859-1" ?>
+
+
+
+
+ + + + + +
+ + + 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 + inefficient. Instead, Ant expects you to place your + 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" + 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 + 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 + 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 + SourceSafe control files (vssver.scc) and certain other + files from FileSets.

+

Here's what you probably did:

+
+ + + + + + + + + + + + + + + + + 
+<delete>
+  <fileset dir="${build.src}" includes="**/vssver.scc"/>
+</delete>
+
+
+

You need to switch off the default exclusions, + and it will work:

+
+ + + + + + + + + + + + + + + + + 
+<delete>
+  <fileset dir="${build.src}" includes="**/vssver.scc"
+           defaultexcludes="no"/>
+</delete>
+
+
+

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, + 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 + 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 + higher-level task + into several smaller steps, this behaviour becomes + counter-intuitive. There are a couple of solutions available: +

+
    +
  1. Put the same condition on each of the dependent targets.
    2. + +
  2. Execute the steps using <antcall>, + instead of specifying them inside the depends + attribute.
    3. +
+
+
+ + + + + +
+ + + 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 + <exclude> tags within a <fileset> + is ignored when the FileSet is created. Instead, all of the + <include> elements are processed together, + followed by all of the <exclude> + 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 + <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 + 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 + 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 + 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 + 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 + 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 + will see that the names have the correct case.

+
+
+ + + + + +
+ + + Is Ant supported by my IDE/Editor? + + +
+
+

See the section + on IDE integration on our External Tools and Tasks page.

+
+
+ + + + + +
+ + + 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 + 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 + -emacs switch. To make Ant autodetect + Emacs' compile mode, put this into your + .antrc (contributed by Ville Skyttä).

+
+ + + + + + + + + + + + + + + + + 
+# Detect (X)Emacs compile mode
+if [ "$EMACS" = "t" ] ; then 
+  ANT_ARGS="$ANT_ARGS -emacs" 
+  ANT_OPTS="$ANT_OPTS -Dbuild.compiler.emacs=true" 
+fi 
+
+
+

Alternatively, you can add the following snippet to your + .emacs to make Emacs understand Ant's + output.

+
+ + + + + + + + + + + + + + + + + 
+(require 'compile)
+(setq compilation-error-regexp-alist
+  (append (list 
+     ;; works for jikes
+     '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):\\([0-9]+\\):[0-9]+:[0-9]+:" 1 2 3)
+     ;; works for javac 
+     '("^\\s-*\\[[^]]*\\]\\s-*\\(.+\\):\\([0-9]+\\):" 1 2))
+  compilation-error-regexp-alist))
+
+
+

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:

+
+ + + + + + + + + + + + + + + + + 
+#!/usr/bin/perl
+#
+# May 2001 dirkx@apache.org - remove any
+# [foo] lines from the output; keeping
+# spacing more or less there.
+#
+$|=1;
+while(<STDIN>) {
+	if (s/^(\s+)\[(\w+)\]//) {
+		if ($2 ne $last) {
+			print "$1\[$2\]";
+			$s = ' ' x length($2);
+		} else {
+			print "$1 $s ";
+		};
+		$last = $2;
+	};
+	print;
+};
+
+
+
+
+ + + + + +
+ + + Is there a DTD that I can use to validate my build + files? + + +
+
+

An incomplete DTD can be created by the + <antstructure> task - but this one + has a few problems:

+
    +
  • It doesn't know about required attributes. Only + manual tweaking of this file can help here.
    • + +
  • It is not complete - if you add new tasks via + <taskdef> it won't know about it. See + this + page by Michel Casabianca for a solution to this + problem. Note that the DTD you can download at this page + is based on Ant 0.3.1.
    • + +
  • It may even be an invalid DTD. As Ant allows tasks + writers to define arbitrary elements, name collisions will + happen quite frequently - if your version of Ant contains + the optional <test> and + <junit> tasks, there are two XML + elements named test (the task and the nested child + element of <junit>) with different attribute + lists. This problem cannot be solved; DTDs don't give a + syntax rich enough to support this.
    • +
+
+
+ + + + + +
+ + + How do I include an XML snippet in my build file? + + +
+
+

You can use XML's way of including external files and let + the parser do the job for Ant:

+
+ + + + + + + + + + + + + + + + + 
+<?xml version="1.0"?>
+
+<!DOCTYPE project [
+    <!ENTITY common SYSTEM "file:./common.xml">
+]>
+
+<project name="test" default="test" basedir=".">
+
+  <target name="setup">
+    ...
+  </target>
+
+  &common;
+
+  ...
+
+</project>
+
+
+

will literally include the contents of common.xml where + you've placed the &common; entity.

+

In combination with a DTD, this would look like this:

+
+ + + + + + + + + + + + + + + + + 
+<!DOCTYPE project PUBLIC "-//ANT//DTD project//EN" "file:./ant.dtd" [
+   <!ENTITY include SYSTEM "file:./header.xml">
+]>
+
+
+
+
+ + + + + +
+ + + How do I send an email with the result of my build + process? + + +
+
+

If you are using a nightly build of Ant 1.5 after + 2001-12-14, you can use the built-in MailLogger:

+
+ + + + + + + + + + + + + + + + + 
+         ant -logger org.apache.tools.ant.listener.MailLogger
+
+
+

See the Listeners + & Loggers documentation for details on the properties + required.

+

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:

+
+ + + + + + + + + + + + + + + + + 
+import java.io.*;
+import java.util.*;
+import javax.mail.*;
+import javax.mail.internet.*;
+import org.apache.tools.ant.*;
+
+/**
+ * A simple listener that waits for a build to finish and sends an email
+ * of the results.  The settings are stored in "monitor.properties" and
+ * are fairly self explanatory.
+ *
+ * @author      Will Glozer
+ * @version     1.05a 09/06/2000
+ */
+public class BuildMonitor implements BuildListener {
+    protected Properties props;
+
+    /**
+     * Create a new BuildMonitor.
+     */
+    public BuildMonitor() throws Exception {
+        props = new Properties();
+        InputStream is = getClass().getResourceAsStream("monitor.properties");
+        props.load(is);
+        is.close();
+    }
+
+    public void buildStarted(BuildEvent e) {
+    }
+
+    /**
+     * Determine the status of the build and the actions to follow, now that
+     * the build has completed.
+     *
+     * @param       e       Event describing the build status.
+     */
+    public void buildFinished(BuildEvent e) {
+        Throwable th = e.getException();
+        String status = (th != null) ? "failed" : "succeeded";
+        
+        try {
+            String key = "build." + status;
+            if (props.getProperty(key + ".notify").equalsIgnoreCase("false")) {
+                    return;
+            }
+            
+            Session session = Session.getDefaultInstance(props, null);
+
+            MimeMessage message = new MimeMessage(session);
+            message.addRecipients(Message.RecipientType.TO, parseAddresses(
+                props.getProperty(key + ".email.to")));
+            message.setSubject(props.getProperty(key + ".email.subject"));
+
+            BufferedReader br = new BufferedReader(new FileReader(
+                props.getProperty("build.log")));
+            StringWriter sw = new StringWriter();
+            
+            String line = br.readLine();
+            while (line != null) {
+                sw.write(line);
+                sw.write("\n");
+                line = br.readLine();
+            }
+            br.close();
+            
+            message.setText(sw.toString(), "UTF-8");
+            sw.close();
+            
+            Transport transport = session.getTransport();
+            transport.connect();
+            transport.send(message);
+            transport.close();
+        } catch (Exception ex) {
+            System.out.println("BuildMonitor failed to send email!");
+            ex.printStackTrace();
+        }
+    }
+
+    /**
+     * Parse a comma separated list of internet email addresses.
+     *
+     * @param       s       The list of addresses.
+     * @return      Array of Addresses.
+     */
+    protected Address[] parseAddresses(String s) throws Exception {
+        StringTokenizer st = new StringTokenizer(s, ",");
+        Address[] addrs = new Address[st.countTokens()];
+
+        for (int i = 0; i < addrs.length; i++) {
+            addrs[i] = new InternetAddress(st.nextToken());
+        }
+        return addrs;
+    }
+
+    public void messageLogged(BuildEvent e) {
+    }
+
+    public void targetStarted(BuildEvent e) {
+    }
+
+    public void targetFinished(BuildEvent e) {
+    }
+
+    public void taskStarted(BuildEvent e) {        
+    }
+
+    public void taskFinished(BuildEvent e) {
+    }
+}
+
+
+

With a monitor.properties like this:

+
+ + + + + + + + + + + + + + + + + 
+# configuration for build monitor
+
+mail.transport.protocol=smtp
+mail.smtp.host=<host>
+mail.from=Will Glozer <will.glozer@jda.com>
+
+build.log=build.log
+
+build.failed.notify=true
+build.failed.email.to=will.glozer@jda.com
+build.failed.email.subject=Nightly build failed!
+
+build.succeeded.notify=true
+build.succeeded.email.to=will.glozer@jda.com
+build.succeeded.email.subject=Nightly build succeeded!
+
+
+

monitor.properties should be placed right next + to your compiled BuildMonitor.class. To use it, + invoke Ant like:

+
+ + + + + + + + + + + + + + + + + 
+ant -listener BuildMonitor -logfile build.log
+
+
+

Make sure that mail.jar from JavaMail and + activation.jar from the + Java + Beans Activation Framework are in your CLASSPATH.

+
+
+ + + + + +
+ + + 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 + has been using through the BuildEvent parameter. For + example:

+
+ + + + + + + + + + + + + + + + + 
+public void buildFinished(BuildEvent e) {
+    Hashtable table = e.getProject().getProperties();
+    String buildpath = (String)table.get("build.path");
+    ...
+}
+
+
+

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 + 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:

+
+ + + + + + + + + + + + + + + + + 
+tr -d '\r' < $ANT_HOME/bin/antRun > /tmp/foo
+mv /tmp/foo $ANT_HOME/bin/antRun
+
+
+
+
+ + + + + +
+ + + JavaDoc failed: java.io.IOException: javadoc: cannot execute + + +
+
+

There is a bug in the Solaris reference implementation of + the JDK (see http://developer.java.sun.com/developer/bugParade/bugs/4230399.html). + This also appears to be true under Linux. Moving the JDK to + the front of the PATH fixes the problem.

+
+
+ + + + + +
+ + + <style> or <junit> ignores my + <classpath> + + +
+
+

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 + .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 + 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 + external library is on the CLASSPATH.

+

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 + doesn't load the external library directly, it is the loaded + class that does so.

+

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.

+

Ant's class loader implementation uses Java's + delegation model, see http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ClassLoader.html + the paragraph

+
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 + ClassLoader instance will delegate the search for + the class or resource to its parent class loader before + attempting to find the class or resource itself. The virtual + machine's built-in class loader, called the bootstrap + 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 + 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 + 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:

+
    +
  1. 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.
    2. + +
  2. remove the class that loads the external library from + the CLASSPATH.
    3. +
+

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> + elements in the <taskdef> tasks that point + to the new location of optional.jar. Also, + don't forget to add the new location of + optional.jar to the + <classpath> of your + <style> or <junit> + task.

+

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 + separate archive. Add this separate archive to the + <classpath> of your + <style> or <junit> task + - and make sure the separate archive is not in + CLASSPATH.

+

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 + 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 + various errors when trying to <exec>, fork + <java> or access environment + variables. + + +
+
+

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 + environment variable ANT_OPTS to + -Dos.name=Windows_NT prior to invoking Ant has + been confirmed as a workaround.

+
+
+ + + + + +
+ + + The ant wrapper script of Ant 1.5 fails + for Cygwin if ANT_HOME is set to a Windows style + path. + + +
+
+

This problem has been reported only hours after Ant 1.5 has + been released, see Bug + 10664 and all it's duplicates.

+

A fixed version of the wrapper script can be found here. + Simply replace your script with this version.

+
+
+ +
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + + + diff --git a/proposal/ant-site/anakia/docs/guidelines.html b/proposal/ant-site/anakia/docs/guidelines.html new file mode 100644 index 000000000..500e65350 --- /dev/null +++ b/proposal/ant-site/anakia/docs/guidelines.html @@ -0,0 +1,116 @@ + + + + + + + + + + + + + Apache Ant - Project Guidelines + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Project Guidelines + +
+
+

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.

+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/images/ant_logo_large.gif b/proposal/ant-site/anakia/docs/images/ant_logo_large.gif new file mode 100644 index 0000000000000000000000000000000000000000..e99363b9ff72ab833802411be2f45a208b8c10bd GIT binary patch literal 5360 zcmeHHXIGO6w|&wRK<0taK}~1@LJ5h4uAw6!2Bf!1D1w3%!I7b8LI+Vp6%jBLc|nm0 z3?c-gBp_W3O;7{_HdItZadh+@u5wMa4@4e1m=eQhnwy{JgQbIyn1o<)tXCVK}#SB=7nJr(>d|W1PbqFX?!2rAJ)T z`=F+0u4Q29*0^MF_Ni!QUA+8idikaJ$@a#_F8}kl0xsMNywDYJz9*u*H}Yp!^hB25 zNvshhToEMH2oh^VX^q0P24PxbdwiKFy>Z}Qq3gqW*T*>>4{CbnTSRj$!ueLwn{}XeDou0`mtEeh1ztq;=akajw zx9?6wRCMCWl!T<@f})=Q7Pq0Ptm4wh*u?PYcyFJet)2J&!{+MRPo9UR6_;+b^R6~D z%{^S0oqsqoHvay@2Q3`#XKMeO-v5vP(+2S0;1B>P0}TIV`S&IO^bP<+Yq;{b!fZ6w zAY_zRKbQ|{xz)IKG~7F<@=G(%8{ar`5$90U6cCkDM#MQ^4;kxxF{GhUW7Dzbm_KpF zBKdlk@Y#3;fuOvu;nub8pz80bD+qUTQ*5L+szr6AydEP^nvO5?Pr}e#_p927$JsX? z{i%$F|E~Ekda=V*JYGAonWxZAd1Qc)>VhxdWg(^*)(;D3$_O{VM#}eme5CBROTFDd zbzOR-s`0pf{oFg|)v~i;B@H@%9;-!JbR9~oAjMp+i>j$xCZm24aF^F!ysdm)v9~Mx zT$2z+4SyQp^nG&aVczB|mA!^%iD|byhH7hTSW}@5l?pVub31}NRvE#Aaf$~n&j@S> zq4p_SuhLaA<3Eve`A-w**$NMMf%VEv%6UXNt9JUi!dV$4eK7P{q1lS>ge4xwVjNm` z^xMTJup`Or?b+XRmz9HZ!Yk&Prw!+BYcT!m31#70x+u*UrM9mj$JO>YUyUAnU8!<} zkz18@L3m6&7`fP?tCY1EIvSbB&pmxl*0s*hA&H^?+gicGy_S`W9;dn=!vc>|t76ut z;kcL+2NzXOwdYy{RbQyz3@TV(9oD|u`>kmuOwRKQ9Fh8uF9K~Iq^uQ}aL6LmTlq^% zIaoM#%`StcWTk!Ts%q-$;rbVOD{`0X?j1RWLy-&BPlL#yt*~+P7pCH#vr&{i7;oi7QeXtx;cZh5)*w= zB>Ix0@L0YAK$W}oXdH4<)4ST%re;ozS_osu^jWNm%T5YbsVDf<&gS-nh55gu>kl)e zc>rHIH+7B;?X`p}d{ncJQlT%GIQfp;@1dTQw2KC;_$$HnoMQ26h z6Ib}r=EsiCA9fE)5iU5bnmIc^skDbeYkAaLapWCCT)A@WyQYfFPaanzJMSNwh8-?u zv3B87PS_PE%A(^s`e&M|F8w+~TnPv(HIQKS_4mjr8g6ptWe()xIIjeDX>m_+TEUDe zZ9kRtDt{y9-wv$;o*j@q-4zPd`gzS9oM5}x41&_y8* zM2}lC?Lj|`^+p|Gt%5P9=vT?CiQDx@roEXfi364S)hnAuTAzeN#W^b$ZA`Ird8SND zr=46I6RGg@zp@R8S7^9RcPCEfF;s)iHKFI0DK@#0*uUsFd-`Qna>JfA6Ix=jFspkL zGRPdYkQZbq#_r)v<9_Q}ZS)Fu6uxst$0Gb=Ye?rBC?oBi+bmZc3hfX^@{u%(z{Atm z5~2vDAwWh^;0ZSS5d37eY7-Ylg(}pznF}>QN7Q;5=Vc8ki@iADJ|Ydsz@toyOOD(8 zK39+JSB4MjP2*Gp21={w4JZ}nb0KdA zF!CXzGU7$u@D9lt%K8A(n_Er3c9GQD#o}2w!fyAB?O*K>Nyjnn0-tduzZaZno^#kNy(}ukA`LGt!@G^EoUL?nv1~`%~zeZCV#o)wn$dIb4*w1>{GV z&mBTB1#p0$ho8diSiDUF5>SD&ST{bp_fT-vqX{r9AaM z9duE>rGPmKScjI1Y=bpnukg-roJN$Ohw*v z$$l4E+$Lzrw4zKycKH6Ltf_5RXxdE4xi)V@%_>M-{Yke9CuXb47{E%_!&Ac|vqkqt zWhA-s7XxVUiPvm2gU77hmu#b4>#Eq^$6-53V&lGP6YFcn)y?Rnm(2(+;rbQjA z7PX`LWcHrK3cM9i^bdJvs4S6%r|z3Pjn#BoY{6+`dfo_%59O>2Kwmstx>bvR9qE#nT z<*O;4fkIfm>{z9Nz(VdL3ukr|_@&rJ?%T>+sXshir5s_t3q|V~MZZGn%7&{IldKVi zdQs>QYzgaXHwsNkbh7#}at+R&MtGgSuHHGO^yd)r_cPF=D^FBi{WmaYJpT$B*32E1 zE5rLH4q(V)PIh;oHg&Ypjb@XeCq`3E+MvN6KR|VjYQpM{HvXP}mNB6Vurf{k&DkQk zu2S~-Eat!#zo-@Vt(x^r>mVQusg0YAyYgJ2Re0<2mWY&Zg;yW_WV!cqb`61r7|B?b z@dQ5S`mn;VS+|c#i6Paa)tZlTAHH%sKis~=Xv^7d#RAnVQ}re($i`#^jIJ^4t&UgM z2bmcpb&a7BlIz7$WVk*4vL(}QDEXE&V}R{&93PjntVQPwIGDu3{M+;WhslN?vQsAL z2&vlgmbk1#HgDs(%y;8idazk8}WC?*|zorA)B+2zE z90hvjQI`HzJ1+M{i2uMUqd}am5}l5dP08B%rSw-&*-)7dHF%9YckR-i9xl@0J`EZ_ zpo=0mn@+0n6;FD;>_bZ(7$&G{$isdkfI%FECOa@*3$BTSY5_1A9e4&_6W19!(S)#_ zHk{UqDDK>??r3qqD?Vk_Q%YOy>o5pW&{iTF41aVlOa^_$M&Wi)xSXap05fnxNGq#V zc(F6?gQ~j+ z;(TdTcqc_}%if2>PTz8eb%vVIVba@*&p)OF34`?`4fiJ{A?jgfyc1r}h_kC?8d-BM zGJu6PIt(J#oe`GuPUD{}Gj@DpVWu#n9F;~a-b_;oM}nDc!piOALZ*GJDFin*1Jz-m z>VQ+q(tu;l{K#x4O(G2vPUUGgXoI>(*jt?>8?N_S6xI0I{(d`?C(6kLQ}R*Mc$-DF zsb|McVnDYASAVa}q*A7MXZn?s>pJB!*e6PCT8*ZfUXyVd<@XT>kjnFgvrgvaVr=h^|tmA>; zX7}@_>G48{J{S$1hR>Lqte!L@yv90%fEy>ri5X_sc-B^>z>bbMq@BBe(7Z!b?yGfx z>P_8Qr&K@?@NGpOQITyj!hRDVE@(NqCh}^s+6Vx%GsK~Y_WbRL|6itfb@1%da59u8#@Ypi<+=N{-J-(27;=z#G zBN6n&sC;*l?KZn2wpHa!QpCE2f5zv79TB*JQqwpsi~sbHj;twZKx3YItK`h6u2GnC z*aAl_)%IsNPgaSMDePu`!wpNbZ>n&s2;)Un1HIq(Vz38}w2)W77L}W7OWVhO*|KqX zgN@$y2LTvv({rJP{HD;{{;x8FlG7_&`3?l_v)XRYoQ?05s?P*m&ZZpLlWb_?P|c@U z-$=3<(KcGZG~H!F!2r;l=W@c#NQ%R-Va4OwRg;$+xe+F5ULigpEHkEt7@)Fm2V%#< z8r_j26sl^)WA#Ih6LtozrnV>)ZOVQj#Fzn}vP10Wsk2iNWEz41xvb0tG#Iw>W2G5h zwmK@&I+Fe5a1Ct0?l;Hw7Aurd$X3$j$~Srm{y7mCFwZEme#F#jo660m5cexs*Xqh2 zq{Tdk;PSLu2ZmrI$=R1)$-T4sv9rW}rv60ozFsL~!d(49A%uj3yCQ4@0u3lL`YLO! zZ^zF1=z7U-19AwSoFWhQ9gy7wpl<>Bc_U4LCu_}v2lGf=o}5$1PFlx5e*++k2Y%;4 zi9E2c1NZh1x%npecb=Ti9|Tf|+ERyxd#BF#PPBFBUh7V|9ckVVDMi;+V0S0PmiM3L zPd5=?>EF%GdsGpPx!Tyx9Bdh|RsH9(7nD#%ykTEt)qvOw+#;5qwxy@+&VtxW{$rJe z&ZTz~NlNZIs9X{%hmO9;0;5Q%s4HlU943u~P8~p@y}D20z`}v$7F#1BGQc^mYj{~4IAb^A|bp$gdy;q4qJOhbLLYLA2 zI2VZ)qCzD6y0^#z23U#%5^-R*q&JrVHplWy0Ss7=Y`%dCc@DSbbS2XOCYr1L*FQ{9(&5`sYAtM{AxlZX<5)0(Brs^}(+?4xr3*|v!2c2f6Afex3)SO3 z_#;?wcS#6ML@F@Rz3GEcMh^r`UVMmXUP30h3(;PJ@3CMwgCD~gH28@AlL#>AD0~Q5 z%;~$hi6CTvi6j6@LYKY;qO;L43WWqVna03Bh^lt_Wg>U;1a(6aw zAYlOVx*;ngG=r~A*i}o;TdogD!dPu2!baEZ*KHnR|igU?hg<#@$~Lt zB9H_0!^KDr9bNhzjH3&}6Ojx_?_(Q~YY2FA5M9>y{XKxd5U`MidS?ivJ&`ZuAVWw% z>Eo?HC8fw+(37qIY#5=Ytz d=+z-?c26$&z};u5J9DY0c8M==gg^l6{{hJ+ag+c6 literal 0 HcmV?d00001 diff --git a/proposal/ant-site/anakia/docs/index.html b/proposal/ant-site/anakia/docs/index.html new file mode 100644 index 000000000..35176101f --- /dev/null +++ b/proposal/ant-site/anakia/docs/index.html @@ -0,0 +1,258 @@ + + + + + + + + + + + + + + + + + Apache Ant - Ant + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Ant 1.5.1 + +
+
+

Apache Ant 1.5.1 Released!

+

Version 1.5.1 of Ant has been released. It is available for download + here. +

+
+
+ + + +
+ + Apache Ant + +
+
+

+Apache Ant is a Java-based build tool. In theory, it is kind of like +Make, but without Make's wrinkles. +

+

+Why another build tool when there is already make, gnumake, +nmake, jam, and +others? Because all those tools have limitations that Ant's original author +couldn't live with when developing software across multiple platforms. Make-like +tools are inherently shell-based -- they evaluate a set of dependencies, then +execute commands not unlike what you would issue in a shell. This means that you +can easily extend these tools by using or writing any program for the OS that +you are working on. However, this also means that you limit yourself to the OS, +or at least the OS type such as Unix, that you are working on. +

+

+Makefiles are inherently evil as well. Anybody who has worked on them for any +time has run into the dreaded tab problem. "Is my command not executing +because I have a space in front of my tab!!!" said the original author of +Ant way too many times. Tools like Jam took care of this to a great degree, but +still have yet another format to use and remember. +

+

+Ant is different. Instead of a model where it is extended with shell-based +commands, Ant is extended using Java classes. Instead of writing shell commands, +the configuration files are XML-based, calling out a target tree where various +tasks get executed. Each task is run by an object that implements a particular +Task interface. +

+

+Granted, this removes some of the expressive power that is inherent by being +able to construct a shell command such as +`find . -name foo -exec rm {}`, 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 +<exec> task that +allows different commands to be executed based on the OS that it is executing +on. +

+
+
+ + + +
+ + Documentation + +
+
+

+You can view the documentation for the current release (Apache Ant 1.5.1) +online +

+

+Comprehensive documentation is included in the source and binary distributions. +

+
+
+ + + +
+ + Latest Release + +
+
+

+ You can download the latest release: +

+ +
+
+ + + +
+ + Nightly Builds + +
+
+

+ If you wish to use the latest Ant features, you can try downloading a nightly + build from here +

+
+
+ + + +
+ + Towards Ant2 + +
+
+

+ We are currently hashing out design details for Ant2. Please + read the latest Ant news for more details. +

+
+
+ + + +
+ + Get Involved + +
+
+ +
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/legal.html b/proposal/ant-site/anakia/docs/legal.html new file mode 100644 index 000000000..2f7f34bb6 --- /dev/null +++ b/proposal/ant-site/anakia/docs/legal.html @@ -0,0 +1,124 @@ + + + + + + + + + + + + + + + Apache Ant - Legal Stuff They Make Us Say + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Legal Stuff They Make Us Say + +
+
+

All material on this website is Copyright © 1999-2002, + The Apache Software Foundation.

+

Sun, Sun Microsystems, Solaris, Java, JavaServer Web + Development Kit, and JavaServer Pages are trademarks or + registered trademarks of Sun Microsystems, Inc. UNIX is a + registered trademark in the United States and other countries, + exclusively licensed through X/Open Company, Ltd. Windows, + WindowsNT, and Win32 are registered trademarks of Microsoft + Corp. All other product names mentioned herein and throughout + the entire web site are trademarks of their respective + owners.

+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/mail.html b/proposal/ant-site/anakia/docs/mail.html new file mode 100644 index 000000000..39a1cf869 --- /dev/null +++ b/proposal/ant-site/anakia/docs/mail.html @@ -0,0 +1,164 @@ + + + + + + + + + + + + + Apache Ant - Mailing Lists + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Mailing Lists + +
+
+

Please read the guidelines of + the Jakarta Project before subscribing and posting to any of + the lists below. They apply to Ant's lists as well.

+

The user and dev list are subscriber only lists, this means + you have to subscribe before you can post to the list. These + lists are archived at

+

+

+

+ + + +
+ + User List + +
+
+

+ Medium Traffic + Subscribe + Unsubscribe + Archive +

+

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.

+
+
+ + + +
+ + Developer List + +
+
+

+ High Traffic + Subscribe + Unsubscribe + Archive +

+

This is the list where participating developers of the Ant + 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.

+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/mission.html b/proposal/ant-site/anakia/docs/mission.html new file mode 100644 index 000000000..fe2a2f88c --- /dev/null +++ b/proposal/ant-site/anakia/docs/mission.html @@ -0,0 +1,192 @@ + + + + + + + + + + + + + Apache Ant - Apache Ant Mission + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Board Resolution + +
+
+

Apache Ant is a project of the Apache Software Foundation. It + started as a subproject of the Apache Jakarta Project.

+

This is the resolution to the board that created the Apache Ant + project:

+
+ + + + + + + + + + + + + + + + + 
+Resolution
+==================
+
+WHEREAS, the Board of Directors deems it to be in the best
+interests of the Foundation and consistent with the
+Foundation's purpose to establish a Project Management
+Committee charged with the creation and maintenance of
+open-source software related to the Apache Ant build tool.
+
+NOW, THEREFORE, BE IT RESOLVED, that a Project Management
+Committee (PMC), to be known as the "Apache Ant PMC", be
+and hereby is established pursuant to Bylaws of the Foundation;
+and be it further
+
+RESOLVED, that the Apache Ant PMC be and hereby is
+responsible for the creation and maintenance of the Ant build
+system and related software components; and be it further
+
+RESOLVED, that the office of "Vice President, Apache Ant"
+be and hereby is created, the person holding such office to
+serve at the direction of the Board of Directors as the chair
+of the Apache Ant PMC, and to have primary responsibility
+for management of the projects within the scope of
+responsibility of the Apache Ant PMC; and be it further
+
+RESOLVED, that the persons listed immediately below be and
+hereby are appointed to serve as the initial members of the
+Apache Ant PMC:
+
+Bruce Atherton
+Stefane Bailliez
+Stefan Bodewig
+James Duncan Davidson (Emeritus)
+Peter Donald
+Erik Hatcher
+Diane Holt
+Donald Leslie
+Steve Loughran
+Conor MacNeill
+Costin Manolache
+Sam Ruby
+Jon Skeet
+Magesh Umasankar
+Christoph Wilhelms
+
+NOW, THEREFORE, BE IT FURTHER RESOLVED, that Conor MacNeill be and
+hereby is appointed to the office of Vice President, Apache
+Ant, to serve in accordance with and subject to the
+direction of the Board of Directors and the Bylaws of the
+Foundation until death, resignation, retirement, removal or
+disqualification, or until a successor is appointed; and be it
+further
+
+RESOLVED, that the initial Apache Ant PMC be and hereby is
+tasked with the creation of a set of bylaws intended to
+encourage open development and increased participation in the
+Apache Ant Project.
+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/problems.html b/proposal/ant-site/anakia/docs/problems.html new file mode 100644 index 000000000..494c2b9fe --- /dev/null +++ b/proposal/ant-site/anakia/docs/problems.html @@ -0,0 +1,431 @@ + + + + + + + + + + + + + + + Apache Ant - Having Problems? + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Having Problems? + +
+
+

+ 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 + resolve the problem, then this page will help you collect some of + the relevant information to provide in a bug report. This information + will help the Ant developers understand and resolve the problem. + Of course, not all the steps here will make sense for every problem + you may encounter - these are just some suggestions to point + you in the right direction. +

+ + + +
+ + Read the Manual + +
+
+

+ The first step to take when you have a problem with Ant is to read + the manual entry for the task or + concept that is giving you trouble. In particular, check the + meaning of a task's attributes and nested elements. Perhaps an + attribute is available that would provide the behavior you require. + If you have problems with the manual itself, you can submit a + documentation bug report (see below) to help us improve the Ant + documentation. +

+
+
+ + + +
+ + Examine Debug Output + +
+
+

+ If you're still having a problem, the next step is to try and + gather additional information about what Ant is doing. + Try running Ant with the verbose flag: +

+ ant -verbose +

+ or +

+ ant -v +

+ + This will produce output that starts like the following:

+ + + + +
+ + +Ant version 1.4.1 compiled on October 11 2001
+Buildfile: build.xml
+Detected Java version: 1.3 in: D:\usr\local\java\jdk13\jre
+Detected OS: Windows NT
+parsing buildfile D:\ant\build.xml +with URI = file:D:/ant/build.xml
+Project base dir set to: D:\ant
+  [property] Loading Environment env.
+  [property] Loading D:\ant\conf.properties
+Build sequence for target 'debug' is [debug]
+Complete build sequence is [debug, gensrc, compile, jar, test]
+. . .
+ + +
+

+ You should be able to see from the trace more about what Ant + is doing and why it's taking a particular course of action. + If you need even more information, you can use the + -debug flag rather than + -verbose. + This will generally produce so much + output that you may want to save the output to a file and + analyze it in an editor. You can save the output using the + -logfile <filename> flag, or + using redirection. +

+

+ Once you have all this debug information, how can you use it + to solve your problem? That will depend on the task in question + and the nature of your problem. Each task logs different aspects + of its operation, but it should give you an idea of what is going + on. For example, the <javac> task logs the + reasons why it + chooses to compile particular class files and not others, along + with which compiler it is using and the arguments it will pass + to that compiler. The following partial trace shows why + <javac> is adding one class file but + skipping another. + This is followed by which compiler it will be using, the + arguments that will get passed to the compiler, + and a list of all the class files to be compiled. +

+ + + + +
+ + +[javac] Test.java omitted as D:\classes\Test.class is up to date.
+[javac] Unset.java added as D:\classes\Unset.class is outdated.
+[javac] Compiling 1 source file to D:\classes
+[javac] Using classic compiler
+[javac] Compilation args: -d D:\classes -classpath D:\classes;
+D:\jdk118\classes.zip; -sourcepath D:\src\java -g:none
+[javac] File to be compiled:
+D:\src\java\Unset.java
+ + +
+

+ In many cases, Ant tasks are wrappers around OS commands or + other Java classes. In debug mode, many of these tasks will + print out the equivalent command line, as the + <javac> task + output does. If you are having a problem, it is often useful to + run the command directly from the command line, in the same way + Ant is running it, and see if the problem occurs from there + as well. The problem may be in the command that is being run, + or it may be in the way the Ant task is running the command. + You can also see the effect of changing attribute values on the + generated command line. This can help you to understand whether + you are using the correct attributes and values. +

+
+
+ + + +
+ + Has It Been Fixed? + +
+
+

+ After examining the debug output, if you still believe that the + problem you are having is caused by Ant, chances are that someone + else may have already encountered this problem, and perhaps it has + been fixed. The next step, therefore, may be to try a nightly build + of Ant to see if the problem has been fixed. Nightly builds for Ant + are available from the + + Jakarta web site. While Ant nightly builds are typically quite + stable and are used by + Gump + to build many other Jakarta projects, these builds should + nonetheless be treated as experimental. Note that nightly builds + do not build many of the optional tasks the come with Ant. + A snapshot of these optional tasks is occasionally uploaded to + the nightly download + + area. However, even this snapshot does not contain every + optional task. +

+
+
+ + + +
+ + Has It Been Reported? + +
+
+

+ If the current nightly build doesn't resolve your problem, it is + possible that someone else has reported the issue. It is time to + look at the + Apache Bug Database. This system is easy to use, and it will + let you search the + currently open and resolved bugs to see if your problem has + already been reported. If your problem has been reported, you can + see whether any of the developers have commented, suggesting + workarounds, or the reason for the bug, etc. Or you may have + information to add (see about creating and modifying bug reports + below), in which case, go right ahead and add the information. + If you don't have any additional information, you may just want + to vote for this bug, and perhaps + add yourself to the CC list to follow the progress + of this bug. +

+
+
+ + + +
+ + Filing a Bug Report + +
+
+

+ 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 + an email to the ant-user mailing list + to see if + others have encountered your issue and find out how they may + have worked around it. If after some discussion, you feel it + is time to create + a bug report, this is a simple operation in the bug database. + Please try to provide as much information as possible in order + to assist the developers in resolving the bug. Please try to enter + correct values for the various inputs when creating the bug, such + as which version of Ant you are running, and on which platform, + etc. Once the bug is created, you can also add attachments to + the bug report. +

+

+ What information should you include in your bug report? The + easiest bugs to fix are those that are most easily reproducible, + so it is really helpful if you can produce a small test case that + exhibits the problem. In this case, you would attach the build file + and any other files necessary to reproduce the problem, probably + packed together in an archive. If you can't produce a test case, + you should try to include a snippet from your build file and the + relevant sections from the verbose or debug output from Ant. Try + to include the header information where Ant states the version, + the OS and VM information, etc. As debug output is likely to be + very large, it's best to remove any output that is not + relevant. Once the bug is entered into the bug database, you + will be kept informed by email about progress on the bug. If + you receive email asking for further information, please try to + respond, as it will aid in the resolution of your bug. +

+
+
+ + + +
+ + Asking for an Enhancement + +
+
+

+ 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 + supposed to work. Perhaps it is some additional functionality for + a task that hasn't been thought of yet, or maybe a completely new + task. For these situations, you will + want to raise an enhancement request. Enhancement requests + are managed using the same Apache Bug Database described above. + These are just a different type of bug report. If you look in the + bug database, you will see that one of the severity settings for + a bug is "Enhancement". Just fill the bug report in, + set the severity of the bug to "Enhancement", and + state in the description how you would like to have Ant enhanced. + Again, you should first check whether there are any existing + enhancment requests that cover your needs. If so, just add your + vote to these. +

+
+
+ + + +
+ + Fixing the Bug + +
+
+

+ 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. + The best way to do that is by working with the latest code from CVS. + Alternatively, you can work with the source code available from the + + source distributions. If you + are going to tackle the problem at this level, you may want to + discuss some details first on the ant-dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + ant-dev mailing + list, or enter the bug database as described above and attach the + patch to the bug report. Using the bug database has the advantage + of being able to track the progress of your patch. +

+

+ If you have a patch to submit and are sending it to the + ant-dev mailing list, + prefix "[PATCH]" + to your message subject. Please include any relevant bug numbers. + Patch files should be created with the -u + option of the + diff or cvs diff command. For + example:

+ + diff -u Javac.java.orig Javac.java > javac.diffs

+ + or, if you have source from CVS:

+ + cvs diff -u Javac.java > javac.diffs

+ + + Note: You should give your patch files meaningful names. + This makes it easier for developers who need to apply a number + of different patch files. +

+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/projects.html b/proposal/ant-site/anakia/docs/projects.html new file mode 100644 index 000000000..37f460894 --- /dev/null +++ b/proposal/ant-site/anakia/docs/projects.html @@ -0,0 +1,715 @@ + + + + + + + + + + + + + + + Apache Ant - Related Projects + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + Related Projects + +
+
+

Nothing listed here is directly supported by the Ant + developers, if you encounter any problems with them, please use + the contact information.

+ + + +
+ + AntContrib + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + 1.4.1 and above + +
+ + URL: + + + + http://sourcefoge.net/projects/ant-contrib/ + +
+ + Contact: + + + + project mailing list + +
+ + License: + + + + Apache Software Foundation license + +
+
+
+ + + +
+ + AntDoc + +
+
+

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 + AntDoc GUI. Ant targets may be launched from the generated + AntDoc HTML pages.

+

AntDoc can be run via an Ant task, AntDoc GUI can be run + via an Ant task, or via a JVM launch.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4.1 and higher + +
+ + URL: + + + + http://mapage.noos.fr/antdoc + +
+ + Contact: + + + + Edouard Mercier + +
+ + License: + + + + At the moment, no license is being attached to the tool. + +
+
+
+ + + +
+ + AntHill + +
+
+

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 + build number after every build. Anthill also encourages the + sharing of knowledge within an organization by automatically + updating a project intranet site with artifacts from the + latest build.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + bundles Ant 1.3, is compatible with Ant 1.3 to 1.4.1 + +
+ + URL: + + + + http://www.urbancode.com/projects/anthill/ + +
+ + Contact: + + + + Maciej Zawadzki + +
+ + License: + + + + Mozilla-like license + +
+
+
+ + + +
+ + CruiseControl + +
+
+

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 + also comes bundled with a servlet for viewing the status of + the current build, as well as previous build results.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.2 and higher + +
+ + URL: + + + + http://cruisecontrol.sourceforge.net/ + +
+ + Contact: + + + + Project Mailing Lists and Administrators + +
+ + License: + + + + Release 1.0 has been licensed under the GNU General Public + License. Starting with release 1.1 the license has been + changed to a BSD-like license. + +
+
+
+ + + +
+ + Krysalis Centipede + +
+
+

Krysalis Centipede is a template for a software module; + gives you build with Ant and Site+Documentation with Apache + Cocoon.

+

Centipede is a starter project, empty in many respects, but + has a decent and standardized Ant build file, and some xdocs + that render to HTML using Cocoon. A developer would take + Centipede and use it to start development. After starting, the + build file would evolve as the developer see fit and move away + from the Centipede starting point. Subsequent releases of + Centipede will address the issues found using it, and evolve + on user requests-issues.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + 1.4.1 + +
+ + URL: + + + + http://krysalis.org/centipede/ + +
+ + Contact: + + + + mailing lists + +
+ + License: + + + + The Krysalis Patchy Software License, based on and + fully compatible with the Apache Software Foundation + license + +
+
+
+ + + +
+ + NAnt + +
+
+

NAnt is a .NET based build tool. In theory it is kind of + like make without make's wrinkles. In practice it's a lot like + Ant.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + compatible in spirit. + +
+ + URL: + + + + http://nant.sourceforge.net/ + +
+ + Contact: + + + + project mailing list + +
+ + License: + + + + GNU General Public License + +
+
+
+ + + +
+ + Rant + +
+
+

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.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://sourceforge.net/projects/remoteant/ + +
+ + Contact: + + + + Chris Nelson + +
+ + License: + + + + MIT License + +
+
+
+ + + +
+ + XML Publication + +
+
+

XML Publication is a set of tools to generate Web pages + from desktop documents or other structured documents using + XSLT and Ant.

+ + + + + + + + + + + + + + + + + +
+ + Compatibility: + + + + Ant 1.4 + +
+ + URL: + + + + http://XMLpublication.org/ + +
+ + Contact: + + + + Jean-Marc Vanel + +
+ + License: + + + + GNU General Public License. + +
+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/docs/resources.html b/proposal/ant-site/anakia/docs/resources.html new file mode 100644 index 000000000..d11a6ee4b --- /dev/null +++ b/proposal/ant-site/anakia/docs/resources.html @@ -0,0 +1,1235 @@ + + + + + + + + + + + + + + + Apache Ant - Resources + + + + + + + + +
+ Apache Ant +
+ + + + + + + + + + + + +
+
+
+

Apache Ant

+ +

Documentation

+ +

Get Involved

+ +

Project Managment

+ + 		+ + + +
+ + FAQs + +
+
+ + + +
+ + At Ant's website + +
+
+

Starting with the release of Ant 1.4 the Ant's FAQ is + bundled with the distribution, the most recent version can + always be found at the website.

+ + + + + +
+ + FAQ: + + + + http://jakarta.apache.org/ant/faq.html + +
+
+
+ + + +
+ + jGuru + +
+
+

jGuru hosts an interactive Ant discussion forum and FAQ system

+ + + + + + + + + +
+ + Forum: + + + + http://www.jguru.com/forums/home.jsp?topic=Ant + +
+ + FAQ: + + + + http://www.jguru.com/faq/home.jsp?topic=Ant + +
+
+
+
+
+ + + +
+ + Books + +
+
+

Listed by descending publication date.

+ + + +
+ + Java Development with Ant + +
+
+

Coming soon: August 2002, covers Ant 1.5 +

+ + + + + + + + + +
+ + Authors: + + + + Erik Hatcher and Steve Loughran + +
+ + URL: + + + + http://www.manning.com/antbook/ + +
+
+
+ + + +
+ + Ant: The Definitive Guide + +
+
+

Covers Ant release 1.4.1.

+ + + + + + + + + +
+ + Authors: + + + + Jesse E. Tilly and Eric M. Burke + +
+ + URL: + + + + http://www.oreilly.com/catalog/anttdg/ + +
+
+
+ + + +
+ + Java Tools for eXtreme Programming + +
+
+

This book covers the following XP subjects: +

    +
  • Automated unit and functional testing
    • +
  • Continuous integration through build and deployment automation
    • +
  • The value of refactoring and continuous integration
    • +
  • How Ant, JUnit, JUnitPerf, Cactus, HTTPUnit, and JMeter + can be used to achieve the goals of the XP methodology
    • +
+

+ + + + + + + + + +
+ + Authors: + + + + Richard Hightower and Nicholas Lesiecki + +
+ + URL: + + + + http://www.wiley.com/cda/product/0,,047120708X,00.html + +
+
+
+
+
+ + + +
+ + Articles and Presentations + +
+
+

The following sections list articles and presentations written about Apache Ant. If + you've written something that should be included, please post it to one + of the mailing lists.

+
+
+ + + +
+ + Articles + +
+
+ + + +
+ + Ant in Anger: Using Ant in a Production Development System + +
+
+

This document describes strategies and some basic examples of how to + use Ant in larger team development projects.

+ + + + + + + + + +
+ + Author: + + + + Steve Loughran + +
+ + URL: + + + + http://jakarta.apache.org/ant/ant_in_anger.html + +
+
+
+ + + +
+ + Ant Task Guidelines + +
+
+

This document describes how to write custom Ant tasks, and how to submit + them to potentially be included in Ant.

+ + + + + + + + + +
+ + Author: + + + + Steve Loughran + +
+ + URL: + + + + http://jakarta.apache.org/ant/ant_task_guidelines.html + +
+
+
+ + + +
+ + Automating the build and test process + +
+
+

This article demonstrates an approach to the automated build and test process. Working with Ant 1.3 and the JUnit test framework, it shows how to automate a process that captures pertinent information about each test suite run, generates an attractive report, and e-mails the report.

+ + + + + + + + + +
+ + Author: + + + + Erik Hatcher + +
+ + URL: + + + + http://www.ibm.com/developerworks/java/library/j-junitmail/ + +
+
+
+ + + +
+ + Incremental development with Ant and JUnit + +
+
+

This article explores the benefits of unit testing with Ant and + JUnit, detailing how to develop automated unit tests and integrate them + into your build process.

+ + + + + + + + + +
+ + Author: + + + + Malcolm Davis + +
+ + URL: + + + + http://www-106.ibm.com/developerworks/library/j-ant/?dwzone=java + +
+
+
+ + + +
+ + Automate your build process using Java and Ant + +
+
+

This article provides an introduction to using Ant with some basic + examples and by highlighting some of the important tasks.

+ + + + + + + + + +
+ + Author: + + + + Michael Cymerman + +
+ + URL: + + + + http://www.javaworld.com/javaworld/jw-10-2000/jw-1020-ant.html + +
+
+
+ + + +
+ + Short tutorial in Cactus' (formerly J2EEUnit) documentation + +
+
+

There is a short tutorial on how to use Ant in Cactus' + documentation. It has a slant towards build files that will be used + with Cactus.

+ + + + + + + + + +
+ + Author: + + + + Cactus development team + +
+ + URL: + + + + http://jakarta.apache.org/cactus/howto_ant_primer.html + +
+
+
+ + + +
+ + Developing custom Ant tasks with VisualAge for Java + +
+
+

This article outlines how to integrate Ant into VisualAge for Java, + and how to write and debug custom tasks using the IDE and the + integrated debugger.

+ + + + + + + + + +
+ + Author: + + + + Glenn McAllister + +
+ + URL: + + + + http://www7.software.ibm.com/vad.nsf/data/document2366?OpenDocument&p=1&BCT=1&Footer=1 + +
+
+
+ + + +
+ + Automated builds with VisualAge for Java and Ant + +
+
+

This article shows how you can perform command line builds with a + VisualAge for Java repository.

+ + + + + + + + + +
+ + Author: + + + + Glenn McAllister + +
+ + URL: + + + + http://www7.software.ibm.com/vad.nsf/Data/Document4366?OpenDocument&p=1&BCT=3&Footer=1 + +
+
+
+ + + +
+ + Ant: A Build Tool from the Jakarta Project + +
+
+

This article is from the "Best Practices" section of + Sun's Dot-Com Builder Site.

+ + + + + + + + + +
+ + Author: + + + + Laura Geele Wang + +
+ + URL: + + + + http://dcb.sun.com/practices/profiles/ant.jsp + +
+
+
+ + + +
+ + Making a Mountain Out of an Anthill + +
+
+

This article is from the June 2001 issue of the Java Developer' + Journal. You need to be a registered JDJ subscriber to view this + article.

+ + + + + + + + + +
+ + Author: + + + + Neal Ford + +
+ + URL: + + + + http://www.sys-con.com/java/archivesa.cfm?volume=06&issue=06 + +
+
+
+ + + +
+ + Using Ant and Weblogic EJBs + +
+
+

This article describes how to use Ant to create Weblogic EJBs, and + some workarounds for issues you may encounter.

+ + + + + + + + + +
+ + Author: + + + + Jesse E. Tilly + +
+ + URL: + + + + http://www.onjava.com/pub/a/onjava/2001/06/25/antejb.html + +
+
+
+ + + +
+ + An Introduction to Ant + +
+
+

This article is a short introduction into the basic + concepts of Ant.

+ + + + + + + + + +
+ + Author: + + + + Jayakrishnan Nair + +
+ + URL: + + + + http://varnam.org/articles/ant.html + +
+
+
+ + + +
+ + Using JavaScript with Ant + +
+
+

A tutorial about using JavaScript and XSLT with Ant.

+ + + + + + + + + +
+ + Author: + + + + Dylan Schiemann + +
+ + URL: + + + + http://www.sitepen.com/ant/javascript.html + +
+
+
+ + + +
+ + Building with Ant + +
+
+

Series of articles that describe a framework for web + application development based on Ant and JUnit.

+ + + + + + + + + +
+ + Author: + + + + Alex Chaffee + +
+ + URL: + + + + Introduction: http://softwaredev.earthweb.com/sdtech/article/0,,12065_989631,00.html
+ Directory Structure: http://softwaredev.earthweb.com/sdtech/article/0,,12082_994991,00.html
+ Deployment and Distribution: http://softwaredev.earthweb.com/sdtech/article/0,,12077_998241,00.html + +
+
+
+ + + +
+ + Developing with JAXB and Ant + +
+
+

Series of articles that shows how to use Ant together with + the Java API for XML Binding (JAXB).

+ + + + + + + + + +
+ + Author: + + + + Joseph Shelby + +
+ + URL: + + + + http://www.onjava.com/pub/a/onjava/2002/03/06/jaxant1.html
+ http://www.onjava.com/pub/a/onjava/2002/03/13/jaxbant2.html + +
+
+
+
+
+ + + +
+ + Presentations + +
+
+ + + +
+ + Ant - presented to the Tucson Java Users Group + +
+
+

A PowerPoint technical overview presentation on Ant. Comes complete with a straightforward example demonstrating code compilation, JAR'ing, JUnit testing, JUnit reporting, and Zipping a distribution. A few advanced topics are touched upon like property immutabality and using <antcall> to get around it, build listeners, and writing custom tasks.

+ + + + + + + + + +
+ + Author: + + + + Erik Hatcher + +
+ + URL: + + + + http://erik.hatcher.net/ant-jug.zip + +
+
+
+ + + +
+ + Ant Build Tool + +
+
+

A PowerPoint presentation on Ant 1.2. It provides a basic overview + of Ant's capabilities.

+ + + + + + + + + +
+ + Author: + + + + Patrick Chanezon + +
+ + URL: + + + + http://people.netscape.com/chanezon/tech/ant/ant_preso.ppt + +
+
+
+ + + +
+ + Ant + +
+
+

A detailed Ant 1.3 PowerPoint presentation, made at the St. Louis Java Users Group + meeting in March 2001. Includes a detailed build file and basic + descriptions of all the built in and optional tasks. Updated for Ant 1.4 in October 2001. + Available in PDF format now.

+ + + + + + + + + +
+ + Author: + + + + Mark Volkmann + +
+ + URL: + + + + http://www.ociweb.com/jnb/files/Ant.pdf + +
+
+
+ + + +
+ + Modern Development Crises + +
+
+

This presentation is an overview of the current state of software + development today. There are a couple of slides that briefly cover + Ant.

+ + + + + + + + + +
+ + Author: + + + + Steve Loughran + +
+ + URL: + + + + http://www.iseran.com/Steve/modern_development_processes.html + +
+
+
+ + + +
+ + When Web Services Go Bad + +
+
+

A presentation from the Web Services + DevCon in March 2002.

+ + + + + + + + + +
+ + Author: + + + + Steve Loughran + +
+ + URL: + + + + http://www.iseran.com/Steve/papers/when_web_services_go_bad.html + +
+
+
+
+
+
+
+
+
+ Copyright © 2000-2002, Apache Software Foundation +
+
+ + + + + + + diff --git a/proposal/ant-site/anakia/xdocs/ant15_todo.xml b/proposal/ant-site/anakia/xdocs/ant15_todo.xml new file mode 100644 index 000000000..99043e123 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/ant15_todo.xml @@ -0,0 +1,220 @@ + + + + + Erik Hatcher + Ant 1.5 Release To-Do List + + + +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ItemDetailsAssigned
Bugzilla bugs under 30or at least address most of them in some wayAll Committers
Document Path datatypeIt's documented, but more hidden than the other typesErik
Novell NetWare supportJeff Tulley
XMLCatalog more integratedSeveral tasks could still use XMLCatalog integration
Make default excludes customizableWith the setting of an ant.default.excludes property?Erik
Fully functional on Java 1.4Fix outstanding java1.4 defects, maybe add an + assertions datatype for java and other tasks (junit?) + which lets people turn on asserts. + Steve + any other help he can get
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ItemDetailsAssigned
SelectorsBruce
Extension utilitiesPort across task that prints out details of extensions for + a certain library/jar, or all jars in a path. Port across task + that generates a manifest (including dependencies and extension + specification) based on a set of jars in path. Port across task + that checks that the list of pre-req extensions are present in + path.Peter
XmlLogger implements BuildLoggerIts currently a BuildListener, lets remove the confusionErik
Dotnet library tweaksupdate to release, add uptodateness, add a web service + import (for Axis interop testing)Steve, in a really long meeting
compiler attribute for rmicStefan
PGP signing task if possibleNot done, but deemed impossible - at least in the 1.5 + time frame.Stefan
JUnit's System.err/.out handlingshowoutput attribute has been added - doesn't work in + some cases yet (same reason as bug PR 7980)Stefan
Base compiler command line switches on the selected + compiler, not the current JDKStefan
<input>Stefan
Make javadoc a real directory based taskStefan
+ + + +

Note: You can sort the report results by clicking on the column-headings.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
New|Assigned|Reopened Bug Reports:
All +
- minus Enhancements +
New|Assigned|Reopened Bug Reports by Component:
Build Process +
- minus Enhancements +
Core +
- minus Enhancements +
Core Tasks +
- minus Enhancements +
Documentation +
- minus Enhancements +
Optional Tasks +
- minus Enhancements +
Other +
- minus Enhancements +
Wrapper Scripts +
- minus Enhancements +
+ +
+ + + diff --git a/proposal/ant-site/anakia/xdocs/antnews.xml b/proposal/ant-site/anakia/xdocs/antnews.xml new file mode 100644 index 000000000..d9dbdace6 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/antnews.xml @@ -0,0 +1,185 @@ + + + + + Conor MacNeill + Stefan Bodewig + Magesh Umasankar + Ant News + + + +
+

October 3, 2002 - Ant 1.5.1 Available !

+

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. +

+
+ +
+

August 19, 2002 - Ant 1.5.1 Beta1 Available !

+

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.

+ +

July 10, 2002 - Ant 1.5 Released!

+

The final version of Ant 1.5 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. +

+
+ +
+

June 24, 2002 - Ant 1.5 Beta3 Available!

+

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. +

+
+ +
+

June 1, 2002 - Ant 1.5 Beta2 Available!

+

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. +

+
+ +
+

Ant 1.5 Beta1 Available !

+

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. +

+
+ +
+

Apr 29, 2002: Ant wins Software Development magazine's + 2002 Productivity Award.

+

+ + Ant has been awarded a 2002 Productivity Award by + Software Development + magazine. Read the + + press release for more information and the full list of winners. +

+
+ +
+

Mar 26, 2002: Ant wins the JavaWorld Editors' Choice + Award

+ +

+ + Ant has won the JavaWorld Editors' Choice Award for + Most Useful Java Community-Developed Technology. + Read the + full article -- or jump directly to the bit about + our award :)

+
+ +
+

Feb 15, 2002: Java 1.4 Support

+

+ Java 1.4 has now been released by Sun. The latest Ant source supports + the new assert statement in the compiler task via the source + attribute. It also contains a compatibility fix needed for some ant tasks + 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. +

+
+ +
+

Have a look at our new cool logo!

+
+ +
+

11 October 2001 Ant 1.4.1 released !

+

Please visit the + + download area. +

+
+ +
+

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 + give you an idea of what Ant2 is going to look like.

+ +

Several details can only be decided in the light of real code + 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.

+
+ +
+

Sun has released an introductory article on Ant on their + Dot-Com Builder site on May 30 2001. See http://dcb.sun.com/practices/profiles/ant.jsp

+
+ +
+

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 + be addressed. +

+ +

+ As we continue to evolve and enhance Ant 1.x, it is now time to define what Ant 2.0 will + encompass. Ant 2.0 will be a major rearchitecting of Ant. It has a number of goals including: +

    +
  • Define the "contract" with build file writers to which Ant will be bound.
    • +
  • Define the "contract" between the Ant core and Task writers.
    • +
  • Make Ant more easily extendable by allowing additional tasks to be "dropped" in.
    • +
  • Allow Ant to function as a component to simplify integration with GUIs and IDEs.
    • +
  • Make Ant more regular and logical.
    • +
+ + It is expected that Ant 2.0 will break Ant 1.x based build files. The intention is to + make this the last time that will happen. +

+ +

+ To advance the definition of Ant, user requirements are now being accepted on the + Ant-Dev mailing list. Any requirement will be accepted for consideration. The + requirements are being collected into a document which is available + on-line. New features will be excepted + until March 21st, 2001. At that time, each requirement will be discussed + for inclusion in an Ant 2.0 requirement document. +

+ +

+ For your reference some of the goals which have shaped the development of Ant 1.x are + available here. These continue to be + relevant to Ant 2.0. +

+ +

+ If you want to shape the future of Ant, join the + Ant-Dev mailing list and contribute + your ideas. +

+
+ + + + diff --git a/proposal/ant-site/anakia/xdocs/contributors.xml b/proposal/ant-site/anakia/xdocs/contributors.xml new file mode 100644 index 000000000..79f3c025c --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/contributors.xml @@ -0,0 +1,12 @@ + + + + Contributors + + + +
+

Copy info from Jakarta here - add new stuff.

+
+ + \ No newline at end of file diff --git a/proposal/ant-site/anakia/xdocs/cvs.xml b/proposal/ant-site/anakia/xdocs/cvs.xml new file mode 100644 index 000000000..94d9d73f8 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/cvs.xml @@ -0,0 +1,41 @@ + + + + + CVS Repository + + + + +
+ +

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):

+ + +cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
+password: anoncvs + + +cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic checkout [module-name] + +

Modules available for access are (click the links to view the + CVS tree via ViewCVS):

+ + + +

If you are not familiar with CVS, Jakarta's + CVS page may hold many helpful hints.

+
+ + \ No newline at end of file diff --git a/proposal/ant-site/anakia/xdocs/external.xml b/proposal/ant-site/anakia/xdocs/external.xml new file mode 100644 index 000000000..f796b4c18 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/external.xml @@ -0,0 +1,1357 @@ + + + + + Stefan Bodewig + External Tools and Tasks + + + + +
+ +

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 + information to one of the mailing lists.

+ +

Nothing listed here is directly supported by the Ant + developers, if you encounter any problems with them, please use + the contact information.

+ +
+ +
+ + +

AspectJ is an + aspect-oriented extension to Java. This task compiles a + source tree using the AspectJ compiler -- AJC.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3
URL:http://aspectj.org/dl
Contact:support@aspectj.org
License:Apache Software License
+ + + + +

Actually, Anakia is more than just an Ant task, it is a an + XML transformation tool based on JDOM, Velocity and Ant.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and later
URL:http://jakarta.apache.org/velocity/anakia.html
Contact:Velocity mailing lists
License:Apache Software License
+ + + + +

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 + codes, XPath, regexp and Relax NG expressions. Includes HTML reporting + (based on junitreport) and a hierarchical grouping system for quickly + configuring large test scripts. +

+ + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5 and later
URL:http://aft.sourceforge.net
Contact:developer + mailing list
License:Apache Software License
+ + + + +

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 + humans of this boring (but important) task.

+ +

Checkstyle can be run via an Ant task or a command line + utility.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 to 1.4.1
URL:http://checkstyle.sourceforge.net/
Contact:Oliver Burn
License:Starting with release 2.0 the license is the GNU + Lesser General Public License. Prior releases were under + the GNU General Public License.
+ + + +

Removes unneeded imports. Formats your import + sections. Flags ambiguous imports.

+ + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3
URL:http://www.euronet.nl/users/tomb/cleanImports/index.html
Contact:Tom Brus
License:Apache Software License
+ + + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4.1 or greater
URL:http://www.thecortex.net/clover
Contact:clover-support@cortexebusiness.com.au
License:Commercial, free licenses available for open source + projects.
+ + + + +

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.

+ +

The task generates build files in any subdirectory (except + for CVS-directories) for you. Only place one build.xml file in + the top and call target 'setup' or + 'rescan'.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and 1.3
URL:http://www.dsdelft.nl/~lemval/ant/
Contact:M.J.P. van Leeuwen
License:License derived from Apache Software License
+ + + + +

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 + the CVS repository via standard http, and downloads all the + files present in it.

+ +

It works from the command line or as an Ant task.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3 or higher
URL:http://cvsgrab.sourceforge.net/
Contact:CVSGrab + user mailing list
License:LGPL
+ + + +

There are two Ant tasks for running the Doxygen + documentation system.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.1 and later
URL:http://www.bgw.org/projects/java/ant/
Contact:Kyle R. Burton
License:Apache Software Foundation License
+ +

and

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5 and later
URL:http://ant-doxygen.sourceforge.net
Contact:Karthik A Kumar
License:Apache Software Foundation License
+ + + +

Builds a JAR file based on class dependencies rather than simply the contents of a directory

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 alpha (built after 2001/08/04) and later
URL:http://genjar.sourceforge.net/
Contact:Jesse Stockall
License:Apache Software Foundation License
+ + + + +

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 + repositories with either flat or maven-like structures. It can + read the dependency list from a Maven project file, a + maven-like dependency file, or directly from the build.xml + file.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5
URL:http://www.discore.com/oz/new/index.htm
Contact:Ozben Evren
License:Apache Software License
+ + + +

Removes unnecessary import statements from a Java source code file.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3
URL:http://importscrubber.sourceforge.net/
Contact:Tom Copeland
License:LGPL
+ + + + +

Checks whether a given directory structure conforms to + certain rules that are defined via nested elements of the + task.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://isvalidator.sourceforge.net/en/isDirValidator.htm
Contact:Iñigo Serrano
License:GNU General Public License
+ + + + +

An Ant Plug-in for the Java Source Code Formatter + Jalopy.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 (or higher)
URL:http://jalopy.sourceforge.net
Contact:http://jalopy.sf.net/contact.html
License:Starting with release 1.0 Beta 6 the license is the + BSD License. Prior releases were under the GNU General + Public License.
+ + + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4.1
URL:http://www.experimentalstuff.com/Technologies/JavaMake/index.html
Contact:Mikhail Dmitriev
License:BSD-like License
+ + + + +

There are three different sets of tasks to help build Java 2 Platform, Micro + Edition (J2ME) applications.

+ +

This set supports CLDC and the K Virtual Machine (KVM):

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3
URL:http://www.dribin.org/dave/j2me_ant/
Contact:Dave Dribin
License:Apache Software License
+ +

And this set works with the J2ME Wireless Toolkit and MIDP + for PalmOS:

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3
URL:http://www.stampysoft.com/ant/
Contact:Josh Eckels
License:MIT License
+ +

With Antenna, you can compile, preverify, package, and + obfuscate your MIDP applications, as well as convert them to + PRC files designed to run on MIDP for PalmOS. The tasks are + mostly built around the Wireless Toolkit and the free + RetroGuard obfuscator, with some additional gimmicks like + automatic version numbering.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4.1 or later
URL:http://antenna.sourceforge.net/
Contact:Jörg Pleumann
License:GNU Lesser General Public License
+ + + + + +

Ant tasks that generate record classes for VisualAge for + Java from Cobol copy books.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://glezen.org/javarec/
Contact:Paul Glezen
License:Apache Software License
+ + + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant >= 1.5
URL:http://jcsc.sourceforge.net/
Contact:Ralph Jocham
License:GNU General Public License
+ + + + +

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.

+ + + + + + + + + + + + + + +
Compatibility:Ant 1.4 and later
URL: + http://www.thaiopensource.com/relaxng/jing-ant.html
License:BSD-like
+ + + + +

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 + time. jMetra is best utilized by integrating it with your + project's scheduled build process.

+ +

It works from the command line or using several provided + Ant tasks.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 and higher
URL: + http://www.jmetra.com/ +
Contact: + R Todd Newton + +
License:Commercial, free licenses for open source projects and + evaluations.
+ + + + +

+ + JNI is a free toolkit that makes easy work of + integrating Java and C through the Java Native + Interface (JNI). It includes a code generator that + generates both Java "proxy" classes to access C + "peer" classes, and C "proxy" classes to access + Java "peer" classes or interfaces. It also + includes a core library with a simplified JVM + interface as well as "helper" classes to ease + working with the JNI data types. The code + generation is driven by an XML project file that + can be created with the assistance of the GUI + Project Manager. The code generation can be + invoked either from Ant or from the + GUI. Includes a comprehensive printable PDF User + Guide and plenty of examples.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://jnipp.sf.net/
Contact:Phillip E. Trewhella
License:GNU LGPL
+ + + + +

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 + docs/ant/jrun.html.

+ +

Note that the service pack must be installed on top of an + existing JRun 4 installation.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 or higher
URL:http://dynamic.macromedia.com/bin/MM/software/trial/hwswrec.jsp?product=jrun_sp
Contact:Brian Deitte
License:Commercial
+ + + + +

A build-time architectural testing tool, designed + to maintain clean layering / tiering / modularity. + Macker works against compiled class files, checking + dependencies between classes against a set of + pattern-based access rules you specify for your + project in an XML rules file. Macker doesn't presume + anything about your architecture -- you write the + rules, and Macker keeps you honest about them.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5 and higher (1.4 untested but may work)
URL:http://innig.net/macker/
Contact:Paul Cantrell
License:GNU GPL 2.0
+ + + + +

PMD checks Java source code for unused variables, + unnecessary object creation, etc

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 and higher
URL:http://pmd.sf.net/
Contact:Tom Copeland
License:Apache Software Foundation License
+ + + + +

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.

+ + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 or above
URL:http://www.dallaway.com/ant/
Contact:Richard Dallaway
License:LGPL
+ + + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5.1 and later
URL:http://serialver.sourceforge.net/
Contact:developer mailing list
License:Apache Software License
+ + + + +

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. + But it can also:

+
    +
  • handle multiple transformations, in parallel or pipelined.
    • +
  • enable transformations that split or merge files
    • +
  • process non-XML files, especially HTML (based on JTidy)
    • +
  • apply non-XSLT transformation, especially "regular + fragmentations"
    • +
  • use any custom XMLReader or XMLFilter class to handle new file + formats and transformation techniques.
    • +
+ + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://www.langdale.com.au/styler/
Contact:Arnold deVos
License:LGPL
+ + + + +

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, + expanding or collapsing imports and even organising them into + pre-determined groups.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3 and later
URL:http://www.chive.com/tim.htm
Contact:support@chive.com
License:Commercial
+ + + + +

TiniAnt is an Ant task to support building applications for + the TINI.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 to 1.4.1
URL:http://tiniant.sourceforge.net/
Contact:Sean Kelly
License:BSD-like license
+ + + + +

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 + single-click launching using Java Web Start or into single + Java Archive installers that serve up their content through a + built-in, multi-threaded, ultra light-weight web server.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and 1.3
URL:http://www.geocities.com/vamp201/ant.html
Contact:Gerald Bauer
License:GNU General Public License
+ + + + +

WOProject provides a set of tools to work with + WebObjects 5.1 + independent from platform and IDE. It significantly + improves developer productivity + and makes complex project structures more flexible compared to + traditional Makefile-based approach. +

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://objectstyle.org/woproject/
Contact:Andrus Adamchik
License:Apache license
+ + + + +

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 + descriptors). Templates and matching tasks are provided to generate + EJB and web application deployment descriptors. +

+ + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://sourceforge.net/projects/xdoclet/
License:BSD license
+ + + + +

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 + want to allow XML insertion and removal, or attribute + changes. The emphasis is on providing the simplest means to + perform common XML replacements

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 and later
URL:http://www.oopsconsultancy.com/software/xmltask.html
Contact:xmltask@oopsconsultancy.com
License:GNU General Public License
+ + + + +

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 + supports multiple Jar files at once and makes use of + patternsets and regular expressions to specify elements, which + should be left unobfuscated. Additionally it can be used to + produce patches for obfuscated applications that have already + been deployed.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5 and later
URL:http://www.yworks.com/products/yguard
Contact:yGuard@yWorks.com
License:Library: LGPL, Task: Commercial
+ + +
+ +
+ + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4 and later
URL:http://dione.zcu.cz/~toman40/miniRMI/
Contact:Petr Toman
License:Gnu Lesser Public License
+ + +
+ +
+ + + +

A plugin that integrates Ant into the jEdit editor.

+ + + + + + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.3
URL:http://plugins.jedit.org/plugins/AntFarm
Contact:jEdit developers mailinglist
License:Apache Software License
+ + + + +

An AddIn that integrates Ant with the JDeveloper IDE

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4.1
URL:http://www.erudra.com/antman/index.html
Contact:Ashok Sridhar
License:GNU General Public License
+ + + + +

An OpenTool that integrates Ant into the JBuilder IDE.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and 1.3
URL:http://www.dieter-bogdoll.de/java/AntRunner/
Contact:Dieter Bogdoll
License:GNU General Public License
+ + + + +

A plugin that integrates Ant into the Jext editor.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and 1.3
URL:ftp://jext.sourceforge.net/pub/jext/plugins/AntWork.zip
Contact:Klaus Hartlage
License:GNU General Public License
+ + + + +

Eclipse is a universal tool platform with Ant integration.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.3 - 1.4.1
URL:http://www.eclipse.org
Contact:news://news.eclipse.org/eclipse.tools
License:Common Public License Version 1.0
+ + + + +

+ 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 + as WAR and EAR files. The tool is ant based, and can be used with + as a GUI for general ant development, providing form based entry + of task attributes, and an animated display of task + execution. +

+ + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.3 and docs; adds a jar of extra tasks + to any existing ant installation under ANT_HOME
URL:http://www.bluestone.com/products/hp-as/
License:Proprietary but free to download
+ + + + +

Java IDE with refactoring support and Ant integration.

+ + + + + + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.3
URL:http://www.intellij.com/idea/
Contact:support@intellij.com
License:Commercial
+ + + + +

The Java Development Environment for Emacs (JDEE) supports + Apache Ant as one of three built-in ways to build your + applications.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and later
URL:http://jde.sunsite.dk/
Contact:JDEE Mailing list.
License:GNU General Public License
+ + + + +

A module that integrates Ant into the NetBeans or Sun ONE Studio (formerly Forte for Java) IDEs.

+ + + + + + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.4.1
URL:http://ant.netbeans.org/
Contact:nbdev@netbeans.org
License:Sun Public License
+ + + + +

Java IDE with support for Ant.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.5.1
URL:http://otn.oracle.com/products/jdev/
Contact:jdeveloperbeta_us@oracle.com
License:Commercial
+ + + + +

WSAD features Ant integrate by virtue of being built on the Eclipse tools platform.

+ + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.4.1
Article:Ant Integration Part1
License:Commercial
+ + +
+ + + diff --git a/proposal/ant-site/anakia/xdocs/faq.xml b/proposal/ant-site/anakia/xdocs/faq.xml new file mode 100644 index 000000000..7c0c6962e --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/faq.xml @@ -0,0 +1,1175 @@ + + + + + Stefan Bodewig + Frequently Asked Questions + + + + + Where do I find the latest version of this + document? + +

The latest version can always be found at Ant's homepage + http://jakarta.apache.org/ant/faq.html.

+ + + + + How can I contribute to this FAQ? + +

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 + section of this + page.

+ + + + + How do you create the HTML version of this + FAQ? + + +

We use + Anakia + to render the HTML version from the original XML file.

+ +

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 + jakarta-site2 module checked out from CVS as + 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.

+ + + + + + + + What is Apache Ant? + +

Ant is a Java-based build tool. In theory, it is kind of + like Make, without Make's wrinkles and with the full + portability of pure Java code.

+ + + + + Why do you call it Ant? + + +

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 + 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 + 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 + 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 + 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 + Ant 1.1, released on 19 July 2000. The complete release + history:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Ant VersionRelease Date
1.119 July 2000
1.224 October 2000
1.33 March 2001
1.43 September 2001
1.4.111 October 2001
1.510 July 2002
1.5.13 October 2002
+ + + + + + + + I get checksum errors when I try to extract the + tar.gz distribution file. Why? + +

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 + 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 + 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 + build file? + + +

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 can I use Jikes-specific command-line + switches? + + + +

A couple of switches are supported via "magic" + properties:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
switchpropertydefault
+Ebuild.compiler.emacsfalse == not set
+Pbuild.compiler.pedanticfalse == not set
+Fbuild.compiler.fulldependfalse == not set
(Only for Ant < 1.4; replaced by the + nowarn + attribute of the <javac> + task after that.)

-nowarn		build.compiler.warningstrue == not set
+ +

With Ant >= 1.5, you can also use nested + <compilerarg> elements with the + <javac> task.

+ + + + + + How do I include a < character in my command-line arguments? + +

The short answer is "Use: &lt;".

+ +

The long answer is that this probably won't do what you + want anyway (see the next + section).

+ + + + + How do I redirect standard input or standard output + in the <exec> task? + +

Say you want to redirect the standard input stream of the + cat command to read from a file, something + like:

+ + cat < foo +]]> + +

and try to translate it into

+ + + + + +]]> + +

This will not do what you expect. The input redirection is + performed by your shell, not the command itself, so this + should read:

+ + + + + +]]> + +

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:

+ + + +]]> + +

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 + batch file or shell script (plus any arguments to the script) + as a single command, using the /c or + -c switch, respectively. See + the above section + for example <exec> tasks + executing sh. For batch files, use something like:

+ + + +]]> + + + + + + 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, + 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 + 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: + 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:

+ + + + + + + + + + + + + + +]]> + +

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 + <condition> task.

+ + + + + + + + + + + + + + + + + + + + + + + + +]]> + +

This version takes advantage of two things:

+ +
    +
  • If a property a has not been set, + ${a} will evaluate to ${a}.
    • + +
  • To get a literal $ in Ant, you have to + escape it with another $ - this will also break + the special treatment of the ${ sequence.
    • +
+ +

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 + <isset>:

+ + + + + + + + + + + + +]]> + +

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 + the language, to say nothing of the added maintenance in requiring + two languages to implement a single system. See the + + <script> task documentation for more + details.

+ + + + + How can I include national characters like German + umlauts in my build file? + + +

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 + 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 + 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 + inefficient. Instead, Ant expects you to place your + 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" + 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 + 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 + 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 + SourceSafe control files (vssver.scc) and certain other + files from FileSets.

+ +

Here's what you probably did:

+ + + + + +]]> + +

You need to switch off the default exclusions, + and it will work:

+ + + +]]> + +

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, + 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 + 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 + higher-level task + into several smaller steps, this behaviour becomes + counter-intuitive. There are a couple of solutions available: +

+ +
    +
  1. Put the same condition on each of the dependent targets.
    2. + +
  2. Execute the steps using <antcall>, + instead of specifying them inside the depends + attribute.
    3. +
+ + + + + + 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 + <exclude> tags within a <fileset> + is ignored when the FileSet is created. Instead, all of the + <include> elements are processed together, + followed by all of the <exclude> + 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 + <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 + 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 + 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 + 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 + 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 + 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 + will see that the names have the correct case.

+ + + + + + + Is Ant supported by my IDE/Editor? + +

See the section + on IDE integration on our External Tools and Tasks page.

+ + + + + 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 + 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 + -emacs switch. To make Ant autodetect + Emacs' compile mode, put this into your + .antrc (contributed by Ville Skyttä).

+ + + +

Alternatively, you can add the following snippet to your + .emacs to make Emacs understand Ant's + output.

+ + + +

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:

+ + ) { + if (s/^(\s+)\[(\w+)\]//) { + if ($2 ne $last) { + print "$1\[$2\]"; + $s = ' ' x length($2); + } else { + print "$1 $s "; + }; + $last = $2; + }; + print; +}; +]]> + + + + + + + + Is there a DTD that I can use to validate my build + files? + + + +

An incomplete DTD can be created by the + <antstructure> task - but this one + has a few problems:

+ +
    +
  • It doesn't know about required attributes. Only + manual tweaking of this file can help here.
    • + +
  • It is not complete - if you add new tasks via + <taskdef> it won't know about it. See + this + page by Michel Casabianca for a solution to this + problem. Note that the DTD you can download at this page + is based on Ant 0.3.1.
    • + +
  • It may even be an invalid DTD. As Ant allows tasks + writers to define arbitrary elements, name collisions will + happen quite frequently - if your version of Ant contains + the optional <test> and + <junit> tasks, there are two XML + elements named test (the task and the nested child + element of <junit>) with different attribute + lists. This problem cannot be solved; DTDs don't give a + syntax rich enough to support this.
    • +
+ + + + + How do I include an XML snippet in my build file? + +

You can use XML's way of including external files and let + the parser do the job for Ant:

+ + + + +]> + + + + + ... + + + &common; + + ... + + +]]> + +

will literally include the contents of common.xml where + you've placed the &common; entity.

+ +

In combination with a DTD, this would look like this:

+ + +]> +]]> + + + + + How do I send an email with the result of my build + process? + + + +

If you are using a nightly build of Ant 1.5 after + 2001-12-14, you can use the built-in MailLogger:

+ + + +

See the Listeners + & Loggers documentation for details on the properties + required.

+ +

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:

+ + + +

With a monitor.properties like this:

+ + +mail.from=Will Glozer + +build.log=build.log + +build.failed.notify=true +build.failed.email.to=will.glozer@jda.com +build.failed.email.subject=Nightly build failed! + +build.succeeded.notify=true +build.succeeded.email.to=will.glozer@jda.com +build.succeeded.email.subject=Nightly build succeeded! +]]> + +

monitor.properties should be placed right next + to your compiled BuildMonitor.class. To use it, + invoke Ant like:

+ + + +

Make sure that mail.jar from JavaMail and + activation.jar from the + Java + Beans Activation Framework are in your CLASSPATH.

+ + + + + + 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 + has been using through the BuildEvent parameter. For + example:

+ + + +

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 + 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:

+ + /tmp/foo +mv /tmp/foo $ANT_HOME/bin/antRun +]]> + + + + + JavaDoc failed: java.io.IOException: javadoc: cannot execute + +

There is a bug in the Solaris reference implementation of + the JDK (see http://developer.java.sun.com/developer/bugParade/bugs/4230399.html). + This also appears to be true under Linux. Moving the JDK to + the front of the PATH fixes the problem.

+ + + + + <style> or <junit> ignores my + <classpath> + + +

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 + .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 + 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 + external library is on the CLASSPATH.

+ +

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 + doesn't load the external library directly, it is the loaded + class that does so.

+ +

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.

+ +

Ant's class loader implementation uses Java's + delegation model, see http://java.sun.com/products/jdk/1.2/docs/api/java/lang/ClassLoader.html + the paragraph

+ +
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 + ClassLoader instance will delegate the search for + the class or resource to its parent class loader before + attempting to find the class or resource itself. The virtual + machine's built-in class loader, called the bootstrap + 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 + 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 + 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:

+ +
    +
  1. 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.
    2. + +
  2. remove the class that loads the external library from + the CLASSPATH.
    3. +
+ +

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> + elements in the <taskdef> tasks that point + to the new location of optional.jar. Also, + don't forget to add the new location of + optional.jar to the + <classpath> of your + <style> or <junit> + task.

+ +

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 + separate archive. Add this separate archive to the + <classpath> of your + <style> or <junit> task + - and make sure the separate archive is not in + CLASSPATH.

+ +

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 + 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 + various errors when trying to <exec>, fork + <java> or access environment + variables. + + + +

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 + environment variable ANT_OPTS to + -Dos.name=Windows_NT prior to invoking Ant has + been confirmed as a workaround.

+ + + + + The ant wrapper script of Ant 1.5 fails + for Cygwin if ANT_HOME is set to a Windows style + path. + + +

This problem has been reported only hours after Ant 1.5 has + been released, see Bug + 10664 and all it's duplicates.

+ +

A fixed version of the wrapper script can be found here. + Simply replace your script with this version.

+ + + + + diff --git a/proposal/ant-site/anakia/xdocs/guidelines.xml b/proposal/ant-site/anakia/xdocs/guidelines.xml new file mode 100644 index 000000000..338d4d757 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/guidelines.xml @@ -0,0 +1,23 @@ + + + + + Project Guidelines + + + + +
+ +

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.

+ +
+ + \ No newline at end of file diff --git a/proposal/ant-site/anakia/xdocs/index.xml b/proposal/ant-site/anakia/xdocs/index.xml new file mode 100644 index 000000000..d13469831 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/index.xml @@ -0,0 +1,125 @@ + + + + + Conor MacNeill + Stefan Bodewig + Ant + + + + +
+

Apache Ant 1.5.1 Released!

+

Version 1.5.1 of Ant has been released. It is available for download + here. +

+
+ +
+ +

+Apache Ant is a Java-based build tool. In theory, it is kind of like +Make, but without Make's wrinkles. +

+ +

+Why another build tool when there is already make, gnumake, +nmake, jam, and +others? Because all those tools have limitations that Ant's original author +couldn't live with when developing software across multiple platforms. Make-like +tools are inherently shell-based -- they evaluate a set of dependencies, then +execute commands not unlike what you would issue in a shell. This means that you +can easily extend these tools by using or writing any program for the OS that +you are working on. However, this also means that you limit yourself to the OS, +or at least the OS type such as Unix, that you are working on. +

+ +

+Makefiles are inherently evil as well. Anybody who has worked on them for any +time has run into the dreaded tab problem. "Is my command not executing +because I have a space in front of my tab!!!" said the original author of +Ant way too many times. Tools like Jam took care of this to a great degree, but +still have yet another format to use and remember. +

+ +

+Ant is different. Instead of a model where it is extended with shell-based +commands, Ant is extended using Java classes. Instead of writing shell commands, +the configuration files are XML-based, calling out a target tree where various +tasks get executed. Each task is run by an object that implements a particular +Task interface. +

+ +

+Granted, this removes some of the expressive power that is inherent by being +able to construct a shell command such as +`find . -name foo -exec rm {}`, 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 +<exec> task that +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 +

+ +

+Comprehensive documentation is included in the source and binary distributions. +

+ +
+ +
+

+ You can download the latest release: +

+ +
+ +
+

+ If you wish to use the latest Ant features, you can try downloading a nightly + build from here +

+ +
+ +
+

+ We are currently hashing out design details for Ant2. Please + read the latest Ant news for more details. +

+
+ +
+ + + + +
+ + + + diff --git a/proposal/ant-site/anakia/xdocs/legal.xml b/proposal/ant-site/anakia/xdocs/legal.xml new file mode 100644 index 000000000..8f0869c9b --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/legal.xml @@ -0,0 +1,30 @@ + + + + + Jon S. Stevens + Legal Stuff They Make Us Say + + + + +
+ +

All material on this website is Copyright © 1999-2002, + The Apache Software Foundation.

+ +

Sun, Sun Microsystems, Solaris, Java, JavaServer Web + Development Kit, and JavaServer Pages are trademarks or + registered trademarks of Sun Microsystems, Inc. UNIX is a + registered trademark in the United States and other countries, + exclusively licensed through X/Open Company, Ltd. Windows, + WindowsNT, and Win32 are registered trademarks of Microsoft + Corp. All other product names mentioned herein and throughout + the entire web site are trademarks of their respective + owners.

+ +
+ + + + diff --git a/proposal/ant-site/anakia/xdocs/mail.xml b/proposal/ant-site/anakia/xdocs/mail.xml new file mode 100644 index 000000000..487237557 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/mail.xml @@ -0,0 +1,57 @@ + + + + + Mailing Lists + + + + +
+ +

Please read the guidelines of + the Jakarta Project before subscribing and posting to any of + the lists below. They apply to Ant's lists as well.

+ +

The user and dev list are subscriber only lists, this means + you have to subscribe before you can post to the list. These + lists are archived at

+ +

+

+

+ + +

+ Medium Traffic + Subscribe + Unsubscribe + Archive +

+ +

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 Traffic + Subscribe + Unsubscribe + Archive +

+ +

This is the list where participating developers of the Ant + 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.

+ +
+ + + \ No newline at end of file diff --git a/proposal/ant-site/anakia/xdocs/mission.xml b/proposal/ant-site/anakia/xdocs/mission.xml new file mode 100644 index 000000000..c284a843b --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/mission.xml @@ -0,0 +1,81 @@ + + + + + Apache Ant Mission + + + +
+ +

Apache Ant is a project of the Apache Software Foundation. It + started as a subproject of the Apache Jakarta Project.

+ +

This is the resolution to the board that created the Apache Ant + project:

+ + +Resolution +================== + +WHEREAS, the Board of Directors deems it to be in the best +interests of the Foundation and consistent with the +Foundation's purpose to establish a Project Management +Committee charged with the creation and maintenance of +open-source software related to the Apache Ant build tool. + +NOW, THEREFORE, BE IT RESOLVED, that a Project Management +Committee (PMC), to be known as the "Apache Ant PMC", be +and hereby is established pursuant to Bylaws of the Foundation; +and be it further + +RESOLVED, that the Apache Ant PMC be and hereby is +responsible for the creation and maintenance of the Ant build +system and related software components; and be it further + +RESOLVED, that the office of "Vice President, Apache Ant" +be and hereby is created, the person holding such office to +serve at the direction of the Board of Directors as the chair +of the Apache Ant PMC, and to have primary responsibility +for management of the projects within the scope of +responsibility of the Apache Ant PMC; and be it further + +RESOLVED, that the persons listed immediately below be and +hereby are appointed to serve as the initial members of the +Apache Ant PMC: + +Bruce Atherton +Stefane Bailliez +Stefan Bodewig +James Duncan Davidson (Emeritus) +Peter Donald +Erik Hatcher +Diane Holt +Donald Leslie +Steve Loughran +Conor MacNeill +Costin Manolache +Sam Ruby +Jon Skeet +Magesh Umasankar +Christoph Wilhelms + +NOW, THEREFORE, BE IT FURTHER RESOLVED, that Conor MacNeill be and +hereby is appointed to the office of Vice President, Apache +Ant, to serve in accordance with and subject to the +direction of the Board of Directors and the Bylaws of the +Foundation until death, resignation, retirement, removal or +disqualification, or until a successor is appointed; and be it +further + +RESOLVED, that the initial Apache Ant PMC be and hereby is +tasked with the creation of a set of bylaws intended to +encourage open development and increased participation in the +Apache Ant Project. + + +
+ + \ No newline at end of file diff --git a/proposal/ant-site/anakia/xdocs/problems.xml b/proposal/ant-site/anakia/xdocs/problems.xml new file mode 100644 index 000000000..244290799 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/problems.xml @@ -0,0 +1,268 @@ + + + + + Conor MacNeill + Having Problems? + + + +
+

+ 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 + resolve the problem, then this page will help you collect some of + the relevant information to provide in a bug report. This information + will help the Ant developers understand and resolve the problem. + Of course, not all the steps here will make sense for every problem + 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 + concept that is giving you trouble. In particular, check the + meaning of a task's attributes and nested elements. Perhaps an + attribute is available that would provide the behavior you require. + If you have problems with the manual itself, you can submit a + 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. + Try running Ant with the verbose flag: +



+ ant -verbose +



+ or +



+ ant -v +



+ + This will produce output that starts like the following:

+ + + + +
+Ant version 1.4.1 compiled on October 11 2001

+Buildfile: build.xml

+Detected Java version: 1.3 in: D:\usr\local\java\jdk13\jre

+Detected OS: Windows NT

+parsing buildfile D:\ant\build.xml +with URI = file:D:/ant/build.xml

+Project base dir set to: D:\ant

+  [property] Loading Environment env.

+  [property] Loading D:\ant\conf.properties

+Build sequence for target 'debug' is [debug]

+Complete build sequence is [debug, gensrc, compile, jar, test]

+. . .

+
+

+ You should be able to see from the trace more about what Ant + is doing and why it's taking a particular course of action. + If you need even more information, you can use the + -debug flag rather than + -verbose. + This will generally produce so much + output that you may want to save the output to a file and + analyze it in an editor. You can save the output using the + -logfile <filename> flag, or + using redirection. +

+

+ Once you have all this debug information, how can you use it + to solve your problem? That will depend on the task in question + and the nature of your problem. Each task logs different aspects + of its operation, but it should give you an idea of what is going + on. For example, the <javac> task logs the + reasons why it + chooses to compile particular class files and not others, along + with which compiler it is using and the arguments it will pass + to that compiler. The following partial trace shows why + <javac> is adding one class file but + skipping another. + This is followed by which compiler it will be using, the + arguments that will get passed to the compiler, + and a list of all the class files to be compiled. +

+ + + + +
+[javac] Test.java omitted as D:\classes\Test.class is up to date.

+[javac] Unset.java added as D:\classes\Unset.class is outdated.

+[javac] Compiling 1 source file to D:\classes

+[javac] Using classic compiler

+[javac] Compilation args: -d D:\classes -classpath D:\classes;

+D:\jdk118\classes.zip; -sourcepath D:\src\java -g:none

+[javac] File to be compiled:

+D:\src\java\Unset.java

+
+ +

+ In many cases, Ant tasks are wrappers around OS commands or + other Java classes. In debug mode, many of these tasks will + print out the equivalent command line, as the + <javac> task + output does. If you are having a problem, it is often useful to + run the command directly from the command line, in the same way + Ant is running it, and see if the problem occurs from there + as well. The problem may be in the command that is being run, + or it may be in the way the Ant task is running the command. + You can also see the effect of changing attribute values on the + 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 + else may have already encountered this problem, and perhaps it has + been fixed. The next step, therefore, may be to try a nightly build + of Ant to see if the problem has been fixed. Nightly builds for Ant + are available from the + + Jakarta web site. While Ant nightly builds are typically quite + stable and are used by + Gump + to build many other Jakarta projects, these builds should + nonetheless be treated as experimental. Note that nightly builds + do not build many of the optional tasks the come with Ant. + A snapshot of these optional tasks is occasionally uploaded to + the nightly download + + 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 + look at the + Apache Bug Database. This system is easy to use, and it will + let you search the + currently open and resolved bugs to see if your problem has + already been reported. If your problem has been reported, you can + see whether any of the developers have commented, suggesting + workarounds, or the reason for the bug, etc. Or you may have + information to add (see about creating and modifying bug reports + below), in which case, go right ahead and add the information. + If you don't have any additional information, you may just want + to vote for this bug, and perhaps + 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 + an email to the ant-user mailing list + to see if + others have encountered your issue and find out how they may + have worked around it. If after some discussion, you feel it + is time to create + a bug report, this is a simple operation in the bug database. + Please try to provide as much information as possible in order + to assist the developers in resolving the bug. Please try to enter + correct values for the various inputs when creating the bug, such + as which version of Ant you are running, and on which platform, + etc. Once the bug is created, you can also add attachments to + the bug report. +

+

+ What information should you include in your bug report? The + easiest bugs to fix are those that are most easily reproducible, + so it is really helpful if you can produce a small test case that + exhibits the problem. In this case, you would attach the build file + and any other files necessary to reproduce the problem, probably + packed together in an archive. If you can't produce a test case, + you should try to include a snippet from your build file and the + relevant sections from the verbose or debug output from Ant. Try + to include the header information where Ant states the version, + the OS and VM information, etc. As debug output is likely to be + very large, it's best to remove any output that is not + relevant. Once the bug is entered into the bug database, you + will be kept informed by email about progress on the bug. If + 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 + supposed to work. Perhaps it is some additional functionality for + a task that hasn't been thought of yet, or maybe a completely new + task. For these situations, you will + want to raise an enhancement request. Enhancement requests + are managed using the same Apache Bug Database described above. + These are just a different type of bug report. If you look in the + bug database, you will see that one of the severity settings for + a bug is "Enhancement". Just fill the bug report in, + set the severity of the bug to "Enhancement", and + state in the description how you would like to have Ant enhanced. + Again, you should first check whether there are any existing + 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. + The best way to do that is by working with the latest code from CVS. + Alternatively, you can work with the source code available from the + + source distributions. If you + are going to tackle the problem at this level, you may want to + discuss some details first on the ant-dev + mailing list. Once you have a fix for the problem, you may submit + the fix as a patch to either the + ant-dev mailing + list, or enter the bug database as described above and attach the + patch to the bug report. Using the bug database has the advantage + of being able to track the progress of your patch. +

+

+ If you have a patch to submit and are sending it to the + ant-dev mailing list, + prefix "[PATCH]" + to your message subject. Please include any relevant bug numbers. + Patch files should be created with the -u + option of the + diff or cvs diff command. For + example:



+ + diff -u Javac.java.orig Javac.java > javac.diffs



+ + or, if you have source from CVS:



+ + cvs diff -u Javac.java > javac.diffs



+ + + Note: You should give your patch files meaningful names. + This makes it easier for developers who need to apply a number + of different patch files. +

+ + + +
+ + + diff --git a/proposal/ant-site/anakia/xdocs/projects.xml b/proposal/ant-site/anakia/xdocs/projects.xml new file mode 100644 index 000000000..65b42d2c5 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/projects.xml @@ -0,0 +1,254 @@ + + + + + Stefan Bodewig + Related Projects + + + + +
+ +

Nothing listed here is directly supported by the Ant + developers, if you encounter any problems with them, please use + the contact information.

+ + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:1.4.1 and above
URL:http://sourcefoge.net/projects/ant-contrib/
Contact:project mailing list
License:Apache Software Foundation license
+ + + + +

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 + AntDoc GUI. Ant targets may be launched from the generated + AntDoc HTML pages.

+ +

AntDoc can be run via an Ant task, AntDoc GUI can be run + via an Ant task, or via a JVM launch.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4.1 and higher
URL:http://mapage.noos.fr/antdoc
Contact:Edouard Mercier
License:At the moment, no license is being attached to the tool.
+ + + + +

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 + build number after every build. Anthill also encourages the + sharing of knowledge within an organization by automatically + updating a project intranet site with artifacts from the + latest build.

+ + + + + + + + + + + + + + + + + + +
Compatibility:bundles Ant 1.3, is compatible with Ant 1.3 to 1.4.1
URL:http://www.urbancode.com/projects/anthill/
Contact:Maciej Zawadzki
License:Mozilla-like license
+ + + + +

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 + also comes bundled with a servlet for viewing the status of + the current build, as well as previous build results.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.2 and higher
URL:http://cruisecontrol.sourceforge.net/
Contact:Project Mailing Lists and Administrators
License:Release 1.0 has been licensed under the GNU General Public + License. Starting with release 1.1 the license has been + changed to a BSD-like license.
+ + + + +

Krysalis Centipede is a template for a software module; + gives you build with Ant and Site+Documentation with Apache + Cocoon.

+ +

Centipede is a starter project, empty in many respects, but + has a decent and standardized Ant build file, and some xdocs + that render to HTML using Cocoon. A developer would take + Centipede and use it to start development. After starting, the + build file would evolve as the developer see fit and move away + from the Centipede starting point. Subsequent releases of + Centipede will address the issues found using it, and evolve + on user requests-issues.

+ + + + + + + + + + + + + + + + + + +
Compatibility:1.4.1
URL:http://krysalis.org/centipede/
Contact:mailing lists
License:The Krysalis Patchy Software License, based on and + fully compatible with the Apache Software Foundation + license
+ + + + +

NAnt is a .NET based build tool. In theory it is kind of + like make without make's wrinkles. In practice it's a lot like + Ant.

+ + + + + + + + + + + + + + + + + + +
Compatibility:compatible in spirit.
URL:http://nant.sourceforge.net/
Contact:project mailing list
License:GNU General Public License
+ + + + +

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.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://sourceforge.net/projects/remoteant/
Contact:Chris Nelson
License:MIT License
+ + + + +

XML Publication is a set of tools to generate Web pages + from desktop documents or other structured documents using + XSLT and Ant.

+ + + + + + + + + + + + + + + + + + +
Compatibility:Ant 1.4
URL:http://XMLpublication.org/
Contact:Jean-Marc Vanel
License:GNU General Public License.
+ + +
+ + + diff --git a/proposal/ant-site/anakia/xdocs/resources.xml b/proposal/ant-site/anakia/xdocs/resources.xml new file mode 100644 index 000000000..18f826afc --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/resources.xml @@ -0,0 +1,445 @@ + + + + + Stefan Bodewig + Resources + + + +
+ + +

Starting with the release of Ant 1.4 the Ant's FAQ is + bundled with the distribution, the most recent version can + always be found at the website.

+ + + + + + +
FAQ:http://jakarta.apache.org/ant/faq.html
+ + + +

jGuru hosts an interactive Ant discussion forum and FAQ system

+ + + + + + + + + + +
Forum:http://www.jguru.com/forums/home.jsp?topic=Ant
FAQ:http://www.jguru.com/faq/home.jsp?topic=Ant
+ +
+ +
+

Listed by descending publication date.

+ + +

Coming soon: August 2002, covers Ant 1.5 +

+ + + + + + + + + + +
Authors:Erik Hatcher and Steve Loughran
URL:http://www.manning.com/antbook/
+ + + + +

Covers Ant release 1.4.1.

+ + + + + + + + + +
Authors:Jesse E. Tilly and Eric M. Burke
URL:http://www.oreilly.com/catalog/anttdg/
+ + + +

This book covers the following XP subjects: +

    +
  • Automated unit and functional testing
    • +
  • Continuous integration through build and deployment automation
    • +
  • The value of refactoring and continuous integration
    • +
  • How Ant, JUnit, JUnitPerf, Cactus, HTTPUnit, and JMeter + can be used to achieve the goals of the XP methodology
    • +
+

+ + + + + + + + + + +
Authors:Richard Hightower and Nicholas Lesiecki
URL:http://www.wiley.com/cda/product/0,,047120708X,00.html
+ + +
+ +
+ +

The following sections list articles and presentations written about Apache Ant. If + you've written something that should be included, please post it to one + of the mailing lists.

+ +
+ +
+ + +

This document describes strategies and some basic examples of how to + use Ant in larger team development projects.

+ + + + + + + + + + +
Author:Steve Loughran
URL:http://jakarta.apache.org/ant/ant_in_anger.html
+ + + +

This document describes how to write custom Ant tasks, and how to submit + them to potentially be included in Ant.

+ + + + + + + + + + +
Author:Steve Loughran
URL:http://jakarta.apache.org/ant/ant_task_guidelines.html
+ + + +

This article demonstrates an approach to the automated build and test process. Working with Ant 1.3 and the JUnit test framework, it shows how to automate a process that captures pertinent information about each test suite run, generates an attractive report, and e-mails the report.

+ + + + + + + + + + +
Author:Erik Hatcher
URL:http://www.ibm.com/developerworks/java/library/j-junitmail/
+ + + +

This article explores the benefits of unit testing with Ant and + JUnit, detailing how to develop automated unit tests and integrate them + into your build process.

+ + + + + + + + + + +
Author:Malcolm Davis
URL:http://www-106.ibm.com/developerworks/library/j-ant/?dwzone=java
+ + + +

This article provides an introduction to using Ant with some basic + examples and by highlighting some of the important tasks.

+ + + + + + + + + + +
Author:Michael Cymerman
URL:http://www.javaworld.com/javaworld/jw-10-2000/jw-1020-ant.html
+ + + +

There is a short tutorial on how to use Ant in Cactus' + documentation. It has a slant towards build files that will be used + with Cactus.

+ + + + + + + + + + +
Author:Cactus development team
URL:http://jakarta.apache.org/cactus/howto_ant_primer.html
+ + + +

This article outlines how to integrate Ant into VisualAge for Java, + and how to write and debug custom tasks using the IDE and the + integrated debugger.

+ + + + + + + + + + +
Author:Glenn McAllister
URL:http://www7.software.ibm.com/vad.nsf/data/document2366?OpenDocument&p=1&BCT=1&Footer=1
+ + + +

This article shows how you can perform command line builds with a + VisualAge for Java repository.

+ + + + + + + + + + +
Author:Glenn McAllister
URL:http://www7.software.ibm.com/vad.nsf/Data/Document4366?OpenDocument&p=1&BCT=3&Footer=1
+ + + +

This article is from the "Best Practices" section of + Sun's Dot-Com Builder Site.

+ + + + + + + + + + +
Author:Laura Geele Wang
URL:http://dcb.sun.com/practices/profiles/ant.jsp
+ + + +

This article is from the June 2001 issue of the Java Developer' + Journal. You need to be a registered JDJ subscriber to view this + article.

+ + + + + + + + + + +
Author:Neal Ford
URL:http://www.sys-con.com/java/archivesa.cfm?volume=06&issue=06
+ + + +

This article describes how to use Ant to create Weblogic EJBs, and + some workarounds for issues you may encounter.

+ + + + + + + + + + +
Author:Jesse E. Tilly
URL:http://www.onjava.com/pub/a/onjava/2001/06/25/antejb.html
+ + + +

This article is a short introduction into the basic + concepts of Ant.

+ + + + + + + + + + +
Author:Jayakrishnan Nair
URL:http://varnam.org/articles/ant.html
+ + + +

A tutorial about using JavaScript and XSLT with Ant.

+ + + + + + + + + + +
Author:Dylan Schiemann
URL:http://www.sitepen.com/ant/javascript.html
+ + + +

Series of articles that describe a framework for web + application development based on Ant and JUnit.

+ + + + + + + + + + +
Author:Alex Chaffee
URL:Introduction: http://softwaredev.earthweb.com/sdtech/article/0,,12065_989631,00.html
+ Directory Structure: http://softwaredev.earthweb.com/sdtech/article/0,,12082_994991,00.html
+ Deployment and Distribution: http://softwaredev.earthweb.com/sdtech/article/0,,12077_998241,00.html
+ + + +

Series of articles that shows how to use Ant together with + the Java API for XML Binding (JAXB).

+ + + + + + + + + + +
Author:Joseph Shelby
URL:http://www.onjava.com/pub/a/onjava/2002/03/06/jaxant1.html
+ http://www.onjava.com/pub/a/onjava/2002/03/13/jaxbant2.html
+ +
+ +
+ + +

A PowerPoint technical overview presentation on Ant. Comes complete with a straightforward example demonstrating code compilation, JAR'ing, JUnit testing, JUnit reporting, and Zipping a distribution. A few advanced topics are touched upon like property immutabality and using <antcall> to get around it, build listeners, and writing custom tasks.

+ + + + + + + + + + +
Author:Erik Hatcher
URL:http://erik.hatcher.net/ant-jug.zip
+ + + +

A PowerPoint presentation on Ant 1.2. It provides a basic overview + of Ant's capabilities.

+ + + + + + + + + + +
Author:Patrick Chanezon
URL:http://people.netscape.com/chanezon/tech/ant/ant_preso.ppt
+ + + +

A detailed Ant 1.3 PowerPoint presentation, made at the St. Louis Java Users Group + meeting in March 2001. Includes a detailed build file and basic + descriptions of all the built in and optional tasks. Updated for Ant 1.4 in October 2001. + Available in PDF format now.

+ + + + + + + + + + +
Author:Mark Volkmann
URL:http://www.ociweb.com/jnb/files/Ant.pdf
+ + + +

This presentation is an overview of the current state of software + development today. There are a couple of slides that briefly cover + Ant.

+ + + + + + + + + + +
Author:Steve Loughran
URL:http://www.iseran.com/Steve/modern_development_processes.html
+ + + +

A presentation from the Web Services + DevCon in March 2002.

+ + + + + + + + + + +
Author:Steve Loughran
URL:http://www.iseran.com/Steve/papers/when_web_services_go_bad.html
+ + +
+ + diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/faq.vsl b/proposal/ant-site/anakia/xdocs/stylesheets/faq.vsl new file mode 100644 index 000000000..fd4c8cfa6 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/stylesheets/faq.vsl @@ -0,0 +1,118 @@ + + + + + ## Defined variables + #set ($bodybg = "#ffffff") + #set ($bodyfg = "#000000") + #set ($bodylink = "#525D76") + #set ($bannerbg = "#525D76") + #set ($bannerfg = "#ffffff") + #set ($subbannerbg = "#828DA6") + #set ($subbannerfg = "#ffffff") + #set ($tablethbg = "#039acc") + #set ($tabletdbg = "#a0ddf0") + #set ($pound = "#" ) + + +#faqs() + + +## This is where the FAQ specific macro's live + +#macro (toc $section) + + + +
+ + $section.getAttributeValue("title") + +
+
+
    + #foreach ($faq in $section.getChildren("faq") ) + #subtoc ($faq) + #end +
+
+
+#end + +#macro (subtoc $faq) + #set ($id = $faq.getAttributeValue("id")) +
  • + $xmlout.outputString($faq.getChild("question"), true) +
    • +#end + +#macro (answers $section) + #foreach ($faq in $section.getChildren("faq") ) + #faq ($faq) + #end +#end + +#macro (faq $faq) + #set ($id = $faq.getAttributeValue("id")) + + + + +
    + + + $xmlout.outputString($faq.getChild("question"), true) + + +
    +
    + #foreach ($item in $faq.getChild("answer").getChildren()) + #if ($item.getName().equals("img")) + #image ($item) + #elseif ($item.getName().equals("source")) + #source ($item) + #elseif ($item.getName().equals("table")) + #table ($item) + #else + $xmlout.outputString($item) + #end + #end +
    +
    +     +#end + +#macro (faqs) + #header() + + + +
    + + Questions + +
    +
    + #set ($allFaqSections = $root.getChildren("faqsection")) + #foreach ( $faqSection in $allFaqSections ) + #toc ($faqSection) + #end +
    +
    + + + + +
    + + Answers + +
    +
    + #foreach ( $faqSection in $allFaqSections ) + #answers ($faqSection) + #end +
    +
    + #footer() +#end diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/project.xml b/proposal/ant-site/anakia/xdocs/stylesheets/project.xml new file mode 100644 index 000000000..93fcf5814 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/stylesheets/project.xml @@ -0,0 +1,44 @@ + + + + Apache Ant + Apache Ant + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl b/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl new file mode 100644 index 000000000..b2ff8e525 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl @@ -0,0 +1,81 @@ + + + + + ## Defined variables + #set ($bodybg = "#ffffff") + #set ($bodyfg = "#000000") + #set ($bodylink = "#525D76") + #set ($bannerbg = "#525D76") + #set ($bannerfg = "#ffffff") + #set ($subbannerbg = "#828DA6") + #set ($subbannerfg = "#ffffff") + #set ($tablethbg = "#039acc") + #set ($tabletdbg = "#a0ddf0") + + +#document() + + +## This is where the common page macro's live + +#macro ( subsection $subsection) + + + +
    + + $subsection.getAttributeValue("name") + +
    +
    + #foreach ( $items in $subsection.getChildren() ) + #if ($items.getName().equals("img")) + #image ($items) + #elseif ($items.getName().equals("source")) + #source ($items) + #elseif ($items.getName().equals("table")) + #table ($items) + #else + $xmlout.outputString($items) + #end + #end +
    +
    +#end + +#macro ( section $section) + + + +
    + + $section.getAttributeValue("name") + +
    +
    + #foreach ( $items in $section.getChildren() ) + #if ($items.getName().equals("img")) + #image ($items) + #elseif ($items.getName().equals("source")) + #source ($items) + #elseif ($items.getName().equals("table")) + #table ($items) + #elseif ($items.getName().equals("subsection")) + #subsection ($items) + #else + $xmlout.outputString($items) + #end + #end +
    +
    +#end + +#macro (document) + #header() + #set ($allSections = $root.getChild("body").getChildren("section")) + #foreach ( $section in $allSections ) + #section ($section) + #end + #footer() +#end diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm b/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm new file mode 100644 index 000000000..524b10288 --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm @@ -0,0 +1,186 @@ +## This is where the common macro's live + +#macro ( table $table) + + #foreach ( $items in $table.getChildren() ) + #if ($items.getName().equals("tr")) + #tr ($items) + #end + #end +
    +#end + +#macro ( tr $tr) + + #foreach ( $items in $tr.getChildren() ) + #if ($items.getName().equals("td")) + #td ($items) + #elseif ($items.getName().equals("th")) + #th ($items) + #end + #end + +#end + +#macro ( td $value) + #if ($value.getAttributeValue("colspan")) + #set ($colspan = $value.getAttributeValue("colspan")) + #end + #if ($value.getAttributeValue("rowspan")) + #set ($rowspan = $value.getAttributeValue("rowspan")) + #end + + + #if ($value.getText().length() != 0 || $value.hasChildren()) + $xmlout.outputString($value, true) + #else +   + #end + + +#end + +#macro ( th $value) + #if ($value.getAttributeValue("colspan")) + #set ($colspan = $value.getAttributeValue("colspan")) + #end + #if ($value.getAttributeValue("rowspan")) + #set ($rowspan = $value.getAttributeValue("rowspan")) + #end + + + #if ($value.getText().length() != 0 || $value.hasChildren()) + $xmlout.outputString($value, true) + #else +   + #end + + +#end + +#macro ( projectanchor $name $value ) + #if ($value.startsWith("http://")) + $name + #else + $name + #end +#end + +#macro ( metaauthor $author $email ) + + +#end + +#macro ( image $value ) + #if ($value.getAttributeValue("width")) + #set ($width=$value.getAttributeValue("width")) + #end + #if ($value.getAttributeValue("height")) + #set ($height=$value.getAttributeValue("height")) + #end + #if ($value.getAttributeValue("align")) + #set ($align=$value.getAttributeValue("align")) + #end + +#end + +#macro ( source $value) +
    + + + + + + + + + + + + + + + + + 
    $escape.getText($value.getText())
    +
    +#end + +#macro ( makeProject ) + #set ($menus = $project.getChild("body").getChildren("menu")) + #foreach ( $menu in $menus ) +

    $menu.getAttributeValue("name")

    +
      + #foreach ( $item in $menu.getChildren() ) + #set ($name = $item.getAttributeValue("name")) +
    • #projectanchor($name $item.getAttributeValue("href"))
      • + #end +
    + #end +#end + +#macro (getProjectImage) + + #set ( $logoString = $project.getChild("logo").getAttributeValue("href") ) + #if ( $logoString.startsWith("/") ) + $project.getChild( + #else + $project.getChild( + #end + +#end + +#macro (header) + + + + + + #set ($authors = $root.getChild("properties").getChildren("author")) + #foreach ( $au in $authors ) + #metaauthor ( $au.getText() $au.getAttributeValue("email") ) + #end + + $project.getChild("title").getText() - $root.getChild("properties").getChild("title").getText() + + + + + + + #getProjectImage() + +
    + + + + + + + + + + + + +
    +
    +
    + #makeProject() + +#end + +#macro (footer) +
    +
    +
    +
    + Copyright © 2000-2002, Apache Software Foundation +
    +
    + + +#end diff --git a/proposal/ant-site/anakia/xdocs/velocity.properties b/proposal/ant-site/anakia/xdocs/velocity.properties new file mode 100644 index 000000000..7327d96fb --- /dev/null +++ b/proposal/ant-site/anakia/xdocs/velocity.properties @@ -0,0 +1,2 @@ +file.resource.loader.path=xdocs/stylesheets +velocimacro.library=templates.vm