Apache IvyDE 2. This is the first release considered as stable since the project as been hosted by the Apache Software Foundation. For more information see the IvyDE home page. This is the first non-beta release of Ivy under Apache and includes some major new features like: enhanced Maven2 compatibility, improved cache management, improved concurrency support and numerous bug fixes and other improvements.

Both plainlistener and xmllistener have an option that makes them echo the project's output into their respective logs. Apache Ivy, "A Java based tool for tracking, resolving and managing project dependencies. More information will be available from the Ant site soon. Until we've finished the migration, you can learn more about Ivy from its Incubator website. For more information see the AntUnit home page. Resource collections group resources, and can be further combined with operators such as union and intersection.

This can be extended by custom resources and custom tasks using resources. NET antlib in preparation will replace the. NET optional tasks which ship in Ant. Support for the version control system Subversion will be only provided as an antlib to be released shortly. NET Ant Library 1. This Ant Library contains support for tools like NUnit as well as the "old". NET tasks of Ant's core. It has been tested Microsoft's frameworks as well as Mono.

Unfortunately it never attracted a developer community of its own. This makes it even less likely that volunteers will start to spend time working on it.

Antidote's development has been stalled for years now, despite some efforts to rejuvenate it by single developers. Therefore the Ant developers have chosen to retire Antidote. Nested elements for namespaced tasks and types may belong to the Ant default namespace as well as the task's or type's namespace. All exceptions thrown by tasks are now wrapped in a buildexception giving the location in the buildfile of the task.

As we've already said in the announcements of Ant 1. For a longer list of fixed bugs and new features see the release notes. If you find anything that hasn't been covered in the manual I bet you did or could be explained better, feel free to help us out in the Wiki.

This is a minor bugfix release that fixes a problem with the javah task on JDK 1. If you don't use javah or VAJ, there is no reason to upgrade. Apache IvyDE will contribute to the classpath of your Java project or you can make it retrieve your dependencies directly into your project. Last but not least Apache IvyDE offer editors of ivy.

The API of IvyDE has been stabilized so that third party plugins can rely on it, while still not complete, and still not advertised as stable in Ivy, support of OSGi has been added, javadoc and source attachement can be edited now one by one, improved stability of the resolve process, improved logging for easier debugging.

This release is expected to work with every version of Ivy 2. The OSGi features require Ivy 2. Home Projects. Ant 1. It allows you to create the suit, which will make you become a tiny being. You can also become the Yellowjacket if you prefer. Ant 1. The configuration files are XML-based, calling out a target tree where various tasks get executed.

For Windows, set the environment variable in the appropriate dialog box and open a new console or, by hand. If you are writing a build file that is always to be used behind the firewall, the setproxy task lets you configure the proxy which it does by setting the JVM properties. If you do this, we strongly recommend using Ant properties to define the proxy host, port, etc, so that individuals can override the defaults.

The Ant team acknowledges that this is unsatisfactory. Setting properties on Ant's command line do not work, because those are Ant properties being set, not JVM options. This means the following does not set up the command line:. One other trouble spot with proxies is with authenticating proxies.

Ant cannot go beyond what the JVM does here, and as it is very hard to remotely diagnose, test and fix proxy-related problems, users who work behind a secure proxy will have to spend much time configuring the JVM properties until they are happy. Note : Since Ant 1. The easiest, and best way is to get these external libraries from JPackage if JPackage has them available. Note: for each such library, you will have to get both the external package itself e.

However, JPackage does not package proprietary software, and since some of the optional packages depend on proprietary JARs, they must be handled as follows. This may violate the spirit of JPackage, but it is necessary if you need these proprietary packages. For example, suppose you want to install support for NetRexx, which JPackage does not support:. To build Ant from source, you can either install the Ant source distribution or clone the Ant repository from Git.

See Source Distribution for details. See Installing Ant for examples on how to do this for your operating system. It does not work with gcj or kjc.

Make sure you have downloaded any auxiliary JARs required to build tasks you are interested in. Note that this will make the auxiliary JAR available for the building of Ant only. You can also get most of the auxiliary JAR files i. See Optional Tasks for instructions on how to do this. The fetch. On most occasions you will not need to explicitly bootstrap Ant since the build scripts do that for you.

However, if the build file you are using makes use of features not yet compiled into the bootstrapped Ant, you will need to manually bootstrap.

Run bootstrap. Ant's build script will try to set executable flags for its shell scripts on Unix -like systems. There are various reasons why the chmod task might fail like when you are running the build script as a different user than the one who installed Ant initially. In this case you can set the Ant property chmod.

The following libraries are needed in Ant's classpath if you are using the indicated feature. Note that only one of the regexp libraries is needed for use with the mappers and Java includes a regexp implementation which Ant will find automatically. You will also need to install the particular Ant optional JAR containing the task definitions to make these tasks available. Ant has a built in diagnostics feature.

If you run ant -diagnostics , Ant will look at its internal state and print it out. This code will check and print the following things. Running ant -diagnostics is a good way to check that Ant is installed. It is also a first step towards self-diagnosis of any problem.