Both lines are based off of Ant 1. We recommend using 1. Currently, Apache Ant 1. Manuals for older releases of Ant can be found here. The checksums are not as strong indicators as the PGP signature. First download the KEYS as well as the asc signature file for the particular distribution. Make sure you get these files from the main distribution directory , rather than from a mirror.
Then verify the signatures using. A command line version of GnuPG is also available for Windows users. Follow the instructions to verify the package. Alternatively, you can verify the checksums on the files. Home Projects. Ant 1. An optional task is a task which typically requires an external library to function.
The optional tasks are packaged together with the core Ant tasks. The external libraries required by each of the optional tasks is detailed in the Library Dependencies section. These external libraries must be added to Ant's classpath, in any of the following ways:. This makes the JAR files available to all Ant users and builds. This allows different users to add new libraries to Ant.
All JAR files added to this directory are available to command-line Ant. On the command line with a -lib parameter. This lets you add new JAR files on a case-by-case basis. Avoid this; it makes the JAR files visible to all Java applications, and causes no end of support calls. See below for details. Where possible, this option is generally to be preferred, as the Ant script itself can determine the best path to load the library from: via relative path from the basedir if you keep the library under version control with your project , according to Ant properties, environment variables, Ivy downloads, whatever you like.
If you are using the binary distribution of Ant, or if you are working from source code, you can easily gather most of the dependencies and install them for use with your Ant tasks.
This is an Ant script that you can run to install almost all the dependencies that the optional Ant tasks need. You may also need to set proxy settings. See the Proxy Settings section for details. Note that not all dependencies are gathered using fetch.
Tasks that depend on commercial software, in particular, will require you to have the commercial software installed in order to be used. The Apache Ant Project also provides additional tasks and types that are available as separately downloaded Ant Libraries. You can see the the list of available Antlibs at the Ant Libraries page.
You can also find tasks and types provided by third-party projects at the External Tools and Tasks page. Usually it is done by some configuration dialog. Sometimes JAR files added to a project are automatically added to Ant's classpath. As the round trip time for diagnosis on the Ant user mailing list can be slow, and because filing bug reports complaining about 'ant. You can also make your Ant script reject this environment variable just by placing the following at the top of the script or in an init target :.
If you are behind a firewall with a proxy server, then Ant needs to be configured with the proxy. Here are the different ways to do this. When you run Ant on Java 5 or above, you could try to use the automatic proxy setup mechanism with -autoproxy.
This is the best option for a non-mobile system. For a laptop, you have to change these settings as you roam. 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. Any configuration problem reported to the user mailing list will probably result ins someone asking you to run the command and show the results, so save time by using it yourself. For diagnostics from within IDE, use the diagnostics task to run the same tests as an Ant option.
This can be added to a diagnostics target in a build file to see what tasks are available under the IDE, what the XML parser and classpath is, etc. If you cannot get Ant installed or working, the Ant user mailing list is the best place to start with any problem. Why the user list, and not the developer list? Because there are more users than developers, so more people who can help you. Release notes of the given version in HTML format.
0コメント