To view Ant's docs, open up a web browser and go to: C:javaapacheantapache-ant-1.7.0docsindex.html - the same content you will find at Apache's web site! ANT Version & Command Line Help. Create and run the batch file 'anthelpcommandline.bat' to see Command Line Help for ANT (in the download. Ant 1.7.0 December 19, 2006 - Ant 1.7.0 Available. Apache Ant 1.7.0 is now available for download. Ant 1.7 introduces a resource framework. Some of the core ant tasks such as are now able to process not only file system resources but also zip entries, tar entries, paths. Code Generator Tool- Command Line & Ant Task: Tool consists of a command line version and an Ant Task. It is implemented by the WSDL2Code class and WSDL2Java class. One can choose to run the main classes directly or use one of the scripts to run the WSDL2Code and WSDL2Java appropriately. Service Archive Wizard - Eclipse Plug-in.
The Maven Artifact Resolver Ant Tasks enable build scripts for Apache Ant 1.7+ to use Maven Artifact Resolver combined to Apache Maven Artifact Resolver Provider to resolve dependencies and install and deploy locally built artifacts.
To integrate the tasks into your build file, copy the Über JAR into your project’s lib directory and use the following snippet to load it:
See the build.xml in the project sources for a complete example build script.
The Ant tasks are tightly integrated with the usual Apache Maven settings.xml. By default, the usual ${user.home}/.m2/settings.xml is used for user settings.
For the global settings, different paths will be tried:
- ${ant.home}/etc/settings.xml
- ${maven.home}/conf/settings.xml
- $M2_HOME/conf/settings.xml
The <settings/> definition is used to change that:
Some settings defined in the settings file or in the POM can also be changed inside the Ant file.
Proxy definitions are used throughout the whole session. There may be multiple proxies set. The proxy to use will be chosen by evaluating the nonProxyHosts on each proxy definition, the first matching proxy will be used for a given remote connection.
Authentication elements are used to access remote repositories. Every authentication definition will be added globally and chosen based on the servers attribute. If this attribute is not set, an authentication has to be referenced explicitly to be used.
Only one local repository can be used at a time.
Remote repositories may be defined directly:
Multiple repositories may be used as a group in every place that is legal for a remote repository:
Note: Currently, only file:, http: and https: protocols are supported for remote repositories.
To suppress any network activity and only use already cached artifacts/metadata, you can use a boolean property:
Project settings deal with locally available information about the build.
The POM is the data type used to determine the target for the install and deploy tasks. If you define a POM without an id based on a full pom.xml file, that POM will be used by default for install and deploy.
If a POM is set via a file parameter its effective model is made available as properties to the Ant project. The properties are prefixed with the ref id of the <pom> element, e.g. ${pom.version} for the example above. Likewise, project properties defined in the POM are accessible via the prefix pom.properties.. If no id has been assigned, the properties use the prefix pom. by default.
<artifact> elements define the artifacts produced by this build that should be installed or deployed.
Dependencies are used to to create classpaths or filesets. They are used by the <resolve>-task, which collects the artifacts belonging to the dependencies transitively.
You need to set a POM that references a file for the install task to work.
You need to set a POM that references a file for the deploy task to work, as that POM file will be deployed to repository.
The <resolve>-task is used to collect and resolve dependencies from remote servers. If no repositories are set explicitly for the task, the repositories referenced by “resolver.repositories” are used. This contains only central by default, but can be overridden by supplying another repository definition with this id.
This task is able to assemble the collected dependencies in three different ways:
- Classpath: The <path> element defines a classpath with all resolved dependencies.
- Files: <files> will assemble a resource collection containing all resolved dependencies and/or copy the files to some directory.
- Properties: <properties> will set properties with the given prefix and the coordinates to the path to the resolved file.
These targets may also be mentioned more than once for the same resolve task, but only one <dependencies> element is allowed.
Scope filters can be set on every target, enumerating included and/or excluded scope names. Exclusions are denoted by prefixing the scope name with - or ! (e.g. provided,!system).
The classpath attribute is a shortcut for the scope filters (e.g. classpath='compile' equals scope='provided,system,compile'). Valid values are “compile”, “runtime”, “test”.
The layout attribute of the <files> element is only allowed when the dir attribute is also given and recognizes the following placeholders to refer to the coordinates of the currently processed artifact:
- {groupId}, e.g. “org.apache.maven.resolver”
- {groupIdDirs}, e.g. “org/apache/maven/resolver”
- {artifactId}, e.g. “maven-resolver-api”
- {version}, e.g. “1.0.0-20140518.181353-123”
- {baseVersion}, e.g. “1.0.0-SNAPSHOT”
- {extension}, e.g. “jar”
- {classifier}, e.g. “sources”
Apache Ant 1.9.7 Download
Downloading Ant
Use the links below to download a binary distribution of Ant fromone of our mirrors. It is good practice toverify the integrityof the distribution files, especially if you are using one of ourmirror sites. In order to do this you must use the signatures fromour main distributiondirectory.
Ant is distributed as zip, tar.gz andtar.bz2 archives - the contents are the same. Pleasenote that the tar.* archives contain file names longerthan 100 characters and have been created using GNU tar extensions.Thus they must be untarred with a GNU compatible version oftar.
In addition the JPackageproject provides RPMs at their own distribution site.
If you do not see the file you need in the links below, please seethe master distributiondirectory or, preferably, its mirror.
Mirror
Apache Ant 1.7.1
You are currently using [preferred]. If you encounter aproblem with this mirror, please select another mirror. If allmirrors are failing, there are backup mirrors (at the end ofthe mirrors list) that should be available.
Current Release of Ant
Currently, Apache Ant 1.7.0 is the best available version, see therelease notes.
.ziparchive:apache-ant-1.7.0-bin.zip[PGP][SHA1][MD5].tar.gzarchive:apache-ant-1.7.0-bin.tar.gz[PGP][SHA1][MD5].tar.bz2archive:apache-ant-1.7.0-bin.tar.bz2[PGP][SHA1][MD5]
Old Ant Releases
Older releases of Ant can be found here. Thosereleases are only provided as zip archives that can beextracted by jar xf archive.zip - we highlyrecommend to not use those releases but upgrade to Ant's latest release.
Verify Releases
It is essential that you verify the integrity of the downloadedfiles using the PGP signature or the SHA1 or MD5 checksums. Thechecksums are not as strong indicators as the PGP signature.
The PGP signatures can be verified using PGP or GPG. Firstdownload the KEYSas well as the asc signature file for the particulardistribution. Make sure you get these files from the main distributiondirectory, rather than from a mirror. Then verify the signaturesusing
% pgpk -a KEYSor
% pgpv apache-ant-1.7.0-bin.tar.gz.asc% pgp -ka KEYSor
% pgp apache-ant-1.7.0-bin.tar.gz.asc% gpg --import KEYS
% gpg --verify apache-ant-1.7.0-bin.tar.gz.asc
Alternatively, you can verify the checksums on the files. Unixprograms called md5/sha1 ormd5sum/sha1sum are included in many unixdistributions. *sum is also available as part of GNUTextutils. Windows users can get binary md5 programs from here, here. fsum supports MD5 andSHA1.
We highly recommend to verify the PGP signature, though.