From efac752f43f8f47c955cc08b2cca77b5cacd9770 Mon Sep 17 00:00:00 2001 From: Jan Materne Date: Tue, 19 Dec 2006 08:02:06 +0000 Subject: [PATCH] Use -autoproxy instead of -noproxy. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@488575 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/install.html | 114 +++++++++++++++++++-------------------- 1 file changed, 56 insertions(+), 58 deletions(-) diff --git a/docs/manual/install.html b/docs/manual/install.html index 7373d48de..7e3b8b7af 100644 --- a/docs/manual/install.html +++ b/docs/manual/install.html @@ -38,7 +38,7 @@ href="http://ant.apache.org/">http://ant.apache.org/. All the main Java IDEs ship with Ant, products such as Eclipse, NetBeans and IntelliJ IDEA. If you install Ant this way you usually get the most recent release of Ant at the time the IDE was released. Some of the IDEs (Eclipse - and NetBeans in particular) ship with extra tasks that only work if + and NetBeans in particular) ship with extra tasks that only work if IDE-specific tools are on Ant's path. To use these on command-line versions of Ant, the relevant JARs need to be added to the command-line Ant as extra libraries/tasks. Note that if it is an IDE task or extension that is @@ -47,40 +47,40 @@ href="http://ant.apache.org/">http://ant.apache.org/.

IDE's can invariably be pointed at different Ant installations. This lets - developers upgrade to a new release of Ant, and eliminate inconsistencies - between command-line and IDE Ant. + developers upgrade to a new release of Ant, and eliminate inconsistencies + between command-line and IDE Ant.

Bundled in Java applications

- Many Java applications, most particularly application servers, ship with + Many Java applications, most particularly application servers, ship with a version of Ant. These are primarily for internal use by the application, using the Java APIs to delegate tasks such as JSP page compilation to the Ant runtime. Such distributions are usually unsupported by everyone. Particularly troublesome are those products that non only ship with their own Ant release, - they add their own version of ANT.BAT or ant.sh to the PATH. If Ant starts - behaving wierdly after installing something, try the + they add their own version of ANT.BAT or ant.sh to the PATH. If Ant starts + behaving wierdly after installing something, try the diagnostics advice.

Source Edition

-

If you prefer the source edition, you can download the source for the latest -Ant release from +

If you prefer the source edition, you can download the source for the latest +Ant release from http://ant.apache.org/srcdownload.cgi. If you prefer the leading-edge code, you can access the code as it is being developed via SVN. The Ant website has details on -accessing SVN. +accessing SVN. All bug fixes will go in against the HEAD of the source tree, and the first -response to many bugreps will be "have you tried the latest version". +response to many bugreps will be "have you tried the latest version". Don't be afraid to download and build a prererelease edition, as everything other than new features are usually stable.

- - + + See the section Building Ant on how to build Ant from the source code. You can also access the @@ -109,7 +109,7 @@ If you wish to use a different JAXP-compliant parser, you should remove from Ant's lib directory.

You can then either put the JARs of your preferred parser into Ant's -lib directory or put the jars on the system classpath. +lib directory or put the jars on the system classpath. Some parts of Ant will fail if you use an old parser, especially one that is not namespace-aware. In particular, avoid the Crimson parser.

@@ -117,7 +117,7 @@ that is not namespace-aware. In particular, avoid the Crimson parser.

For the current version of Ant, you will also need a JDK installed on -your system, version 1.2 or later required, 1.5 or later strongly recommended. +your system, version 1.2 or later required, 1.5 or later strongly recommended. The later the version of Java , the more Ant tasks you get.

@@ -128,8 +128,8 @@ The later the version of Java , the more Ant tasks you get.

The Ant team strongly supports users running Ant on Kaffe and other open source Java runtimes, and so strives to have a product that works - well on those platforms. What appears to work well is Kaffe with - Gnu Classpath and the Xerces and Xalan libraries. + well on those platforms. What appears to work well is Kaffe with + Gnu Classpath and the Xerces and Xalan libraries.

@@ -194,7 +194,7 @@ installed in a short, 8.3 path, such as C:\Ant.

Setup

Before you can run Ant there is some additional set up you -will need to do unless you are installing the RPM +will need to do unless you are installing the RPM version from jpackage.org: