Author: jhm
Date: Mon Oct 16 06:57:50 2006
New Revision: 464498
URL: http://svn.apache.org/viewvc?view=rev&rev=464498
Log:
Document two launch options.
Modified:
ant/core/trunk/docs/manual/running.html
Modified: ant/core/trunk/docs/manual/running.html
URL:
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/running.html?view=diff&rev=464498&r1=464497&r2=464498
==============================================================================
--- ant/core/trunk/docs/manual/running.html (original)
+++ ant/core/trunk/docs/manual/running.html Mon Oct 16 06:57:50 2006
@@ -127,12 +127,23 @@
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
</pre>
<p>For more information about <code>-logger</code> and
<code>-listener</code> see
<a href="listeners.html">Loggers & Listeners</a>.
<p>For more information about <code>-inputhandler</code> see
<a href="inputhandler.html">InputHandler</a>.
+<p>Easiest way of changing the exit-behaviour is subclassing the original main
class:
+<pre>
+public class CustomExitCode extends org.apache.tools.ant.Main {
+ protected void exit(int exitCode) {
+ // implement your own behaviour, e.g. NOT exiting the JVM
+ }
+}
+</pre> and starting Ant with access (<tt>-lib path-to-class</tt>) to this
class.
+</p>
<h3><a name="libs">Library Directories</a></h3>
<p>
@@ -161,7 +172,7 @@
<p>
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 @@
grep -r -n "getPropert" * > ..\grep.txt
</pre>
command. After that I filtered out the often-used but not-so-important values
(most of them
-read-only values): <i>path.separator, ant.home, basedir, user.dir, os.name,
+read-only values): <i>path.separator, ant.home, basedir, user.dir, os.name,
line.separator, java.home, java.version, java.version, user.home,
java.class.path</i><br>
And I filtered out the <i>getPropertyHelper</i> access.</p>
<table border="1">
@@ -284,9 +295,9 @@
<td><code>ant.file.*</code></td>
<td>read only: full filename of the build file of Ant projects
</td>
- <td>This is set to the name of a file by project;
+ <td>This is set to the name of a file by project;
this lets you determine the location of <a href="CoreTasks/import.html">
- <import>-ed</a> files,
+ <import>-ed</a> files,
</td>
</tr>
@@ -455,8 +466,8 @@
<p>
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.
</p>
@@ -538,7 +549,7 @@
</ul>
<p>
-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.
</p>
@@ -572,4 +583,4 @@
</body>
-</html>
+</html>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
