From 31e8fc7aa79612812e799ad94d6fa34a096df17c Mon Sep 17 00:00:00 2001 From: Jan Materne Date: Mon, 16 Oct 2006 13:57:50 +0000 Subject: [PATCH] Document two launch options. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@464498 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/running.html | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-) diff --git a/docs/manual/running.html b/docs/manual/running.html index e69dc6b5d..5c122ce76 100644 --- a/docs/manual/running.html +++ b/docs/manual/running.html @@ -127,12 +127,23 @@ Options: 1 (lowest) to 10 (highest); 5 is the default -nouserlib Run ant without using the jar files from ${user.home}/.ant/lib -noclasspath Run ant without using CLASSPATH + -noproxy Java 1.5 only: do not use the OS proxies + -main <class> override Ant's normal entry point

For more information about -logger and -listener see Loggers & Listeners.

For more information about -inputhandler see InputHandler. +

Easiest way of changing the exit-behaviour is subclassing the original main class: +

+public class CustomExitCode extends org.apache.tools.ant.Main {
+    protected void exit(int exitCode) {
+        // implement your own behaviour, e.g. NOT exiting the JVM
+    }
+}
+
and starting Ant with access (-lib path-to-class) to this class. +

Library Directories

@@ -161,7 +172,7 @@ added to the classpath is as follows:

Note that the CLASSPATH environment variable is passed to Ant using a -lib -option. Ant itself is started with a very minimalistic classpath. +option. Ant itself is started with a very minimalistic classpath. Ant should work perfectly well with an empty CLASSPATH environment variable, something the the -noclasspath option actually enforces. We get many more support calls related to classpath problems (especially quoting problems) than we like. @@ -244,7 +255,7 @@ available via Project instance, I searched for them with a grep -r -n "getPropert" * > ..\grep.txt command. After that I filtered out the often-used but not-so-important values (most of them -read-only values): path.separator, ant.home, basedir, user.dir, os.name, +read-only values): path.separator, ant.home, basedir, user.dir, os.name, line.separator, java.home, java.version, java.version, user.home, java.class.path
And I filtered out the getPropertyHelper access.

@@ -284,9 +295,9 @@ org.apache.tools.ant.Executor implementation specified here. - @@ -455,8 +466,8 @@ org.apache.tools.ant.Executor implementation specified here.

If new properties get added (it happens), expect them to appear under the -"ant." and "org.apache.tools.ant" prefixes, unless the developers have a -very good reason to use another prefix. Accordingly, please avoid using +"ant." and "org.apache.tools.ant" prefixes, unless the developers have a +very good reason to use another prefix. Accordingly, please avoid using properties that begin with these prefixes. This protects you from future Ant releases breaking your build file.

@@ -538,7 +549,7 @@ include:

-The latter method supports the -lib, -nouserlib, -noclasspath options and will +The latter method supports the -lib, -nouserlib, -noclasspath options and will load jars from the specified ANT_HOME. You should start the latter with the most minimal classpath possible, generally just the ant-launcher.jar.

@@ -572,4 +583,4 @@ Here is an example: - + \ No newline at end of file
ant.file.* read only: full filename of the build file of Ant projects This is set to the name of a file by project; + This is set to the name of a file by project; this lets you determine the location of - <import>-ed files, + <import>-ed files,