bodewig 2003/10/07 07:28:25
Modified: docs faq.html
xdocs faq.xml
Log:
Update the delegating-classloader FAQ
Revision Changes Path
1.79 +19 -1 ant/docs/faq.html
Index: faq.html
===================================================================
RCS file: /home/cvs/ant/docs/faq.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- faq.html 23 Sep 2003 11:04:09 -0000 1.78
+++ faq.html 7 Oct 2003 14:28:25 -0000 1.79
@@ -1319,6 +1319,10 @@
<code>CLASSPATH</code> environment variable or
<code>ANT_HOME/lib</code>" for the rest of this
answer.</p>
+ <p>Technically the sentence above isn't true for Ant
1.6
+ and later anymore, but the result is the same. For the sake
+ of this discussion, <code>CLASSPATH</code> and
+ <code>ANT_HOME/lib</code> are identical.</p>
<p>This question collects a common type of problem:
A task
needs an external library and it has a nested classpath
element so that you can point it to this external library, but
@@ -1371,6 +1375,8 @@
<li>remove the class that loads the external library from
the <code>CLASSPATH</code>.</li>
</ol>
+ <p><strong>Using The Second Option with Ant 1.5.4 and
+ Earlier:</strong></p>
<p>The easiest way to do this is to remove
<code>optional.jar</code> from <code>ANT_HOME/lib</code>. If
you do so, you will have to <code><taskdef></code> all
@@ -1397,8 +1403,20 @@
directory, in the <code><style></code> case it is one of
the <code>*Liaison</code> classes in
<code>org/apache/tools/ant/taskdefs/optional</code>.</p>
+ <p><strong>Using The Second Option with Ant 1.6 and
+ later:</strong></p>
+ <p>In Ant 1.6 <code>optional.jar</code> has been
split into
+ multiple jars, each one containing classes with the same
+ dependencies on external libraries. You can move the
+ "offending" jar out of ANT_HOME/lib. For the
+ <code><junit></code> task it would be
+ <code>ant-junit.jar</code> and for <code><style></code>
+ it would be <code>ant-trax.jar</code>,
+ <code>ant-xalan1.jar</code> or <code>ant-xslp.jar</code> -
+ depending on the processor you use.</p>
<p>If you use the option to break up
<code>optional.jar</code>
- for <code><junit></code>, you still have to use a
+ for <code><junit></code> or remove
+ <code>ant-junit.jar</code>, you still have to use a
<code><taskdef></code> with a nested
<code><classpath></code> to define the junit task.</p>
<p class="faq">
1.39 +23 -1 ant/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/ant/xdocs/faq.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- faq.xml 20 Aug 2003 16:07:48 -0000 1.38
+++ faq.xml 7 Oct 2003 14:28:25 -0000 1.39
@@ -1090,6 +1090,11 @@
<code>ANT_HOME/lib</code>" for the rest of this
answer.</p>
+ <p>Technically the sentence above isn't true for Ant 1.6
+ and later anymore, but the result is the same. For the sake
+ of this discussion, <code>CLASSPATH</code> and
+ <code>ANT_HOME/lib</code> are identical.</p>
+
<p>This question collects a common type of problem: A task
needs an external library and it has a nested classpath
element so that you can point it to this external library, but
@@ -1154,6 +1159,9 @@
the <code>CLASSPATH</code>.</li>
</ol>
+ <p><strong>Using The Second Option with Ant 1.5.4 and
+ Earlier:</strong></p>
+
<p>The easiest way to do this is to remove
<code>optional.jar</code> from <code>ANT_HOME/lib</code>. If
you do so, you will have to <code><taskdef></code> all
@@ -1183,8 +1191,22 @@
the <code>*Liaison</code> classes in
<code>org/apache/tools/ant/taskdefs/optional</code>.</p>
+ <p><strong>Using The Second Option with Ant 1.6 and
+ later:</strong></p>
+
+ <p>In Ant 1.6 <code>optional.jar</code> has been split into
+ multiple jars, each one containing classes with the same
+ dependencies on external libraries. You can move the
+ "offending" jar out of ANT_HOME/lib. For the
+ <code><junit></code> task it would be
+ <code>ant-junit.jar</code> and for <code><style></code>
+ it would be <code>ant-trax.jar</code>,
+ <code>ant-xalan1.jar</code> or <code>ant-xslp.jar</code> -
+ depending on the processor you use.</p>
+
<p>If you use the option to break up <code>optional.jar</code>
- for <code><junit></code>, you still have to use a
+ for <code><junit></code> or remove
+ <code>ant-junit.jar</code>, you still have to use a
<code><taskdef></code> with a nested
<code><classpath></code> to define the junit task.</p>
</answer>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
