Author: jglick
Date: Sat Feb 13 15:04:48 2010
New Revision: 909835
URL: http://svn.apache.org/viewvc?rev=909835&view=rev
Log:
Deleting some obsolete FAQ entries.
Modified:
ant/core/trunk/docs/manual/OptionalTasks/junit.html
ant/core/trunk/xdocs/faq.xml
Modified: ant/core/trunk/docs/manual/OptionalTasks/junit.html
URL:
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/OptionalTasks/junit.html?rev=909835&r1=909834&r2=909835&view=diff
==============================================================================
--- ant/core/trunk/docs/manual/OptionalTasks/junit.html (original)
+++ ant/core/trunk/docs/manual/OptionalTasks/junit.html Sat Feb 13 15:04:48 2010
@@ -183,10 +183,7 @@
<td valign="top">includeantruntime</td>
<td valign="top">Implicitly add the Ant classes required to run
the tests and JUnit to the classpath in forked mode.
- <b>Note:</b> Please read the <a
- href="../../faq.html#junit-no-runtime-xml">Ant FAQ</a> if you
- want to set this to <code>false</code> and use the XML formatter
- at the same time.</td>
+ </td>
<td align="center" valign="top">No; default is <code>true</code>.</td>
</tr>
<tr>
@@ -379,12 +376,6 @@
<code>ant.junit.failureCollector</code>. The value has to point to the
directory and
the name of the resulting class (without suffix). It defaults to
<i>java-tmp-dir</i>/FailedTests.</p>
-<p><b>Note:</b> Please read the <a
-href="../../faq.html#junit-no-runtime-xml">Ant FAQ</a> if you want to
-set the fork attribute to <code>true</code>, the includeAntRuntime
-attribute to <code>false</code> and use the XML formatter at the same
-time.</p>
-
<table border="1" cellpadding="2" cellspacing="0">
<tr>
<td width="12%" valign="top"><b>Attribute</b></td>
Modified: ant/core/trunk/xdocs/faq.xml
URL:
http://svn.apache.org/viewvc/ant/core/trunk/xdocs/faq.xml?rev=909835&r1=909834&r2=909835&view=diff
==============================================================================
--- ant/core/trunk/xdocs/faq.xml (original)
+++ ant/core/trunk/xdocs/faq.xml Sat Feb 13 15:04:48 2010
@@ -1566,16 +1566,6 @@
</answer>
</faq>
- <faq id="javadoc-cannot-execute">
- <question>JavaDoc failed: java.io.IOException: javadoc: cannot
execute</question>
- <answer>
- <p>There is a bug in the Solaris reference implementation of
- the JDK (see <a
href="http://developer.java.sun.com/developer/bugParade/bugs/4230399.html";>http://developer.java.sun.com/developer/bugParade/bugs/4230399.html</a>).
- This also appears to be true under Linux. Moving the JDK to
- the front of the PATH fixes the problem.</p>
- </answer>
- </faq>
-
<faq id="delegating-classloader">
<question><style> or <junit> ignores my
<classpath></question>
@@ -1823,68 +1813,6 @@
</answer>
</faq>
- <faq id="winxp-jdk14-ant14">
- <question>When running Ant 1.4 on Windows XP and JDK 1.4, I get
- various errors when trying to <code><exec></code>, fork
- <code><java></code> or access environment
- variables.</question>
-
- <answer>
-
- <p>Ant < 1.5 doesn't recognize Windows XP as a flavor
- of Windows that runs <code>CMD.EXE</code> instead of
- <code>COMMAND.COM</code>. JDK 1.3 will tell Ant that Windows
- XP is Windows 2000 so the problem doesn't show up
- there.</p>
-
- <p>Apart from upgrading to Ant 1.5 or better, setting the
- environment variable <code>ANT_OPTS</code> to
- <code>-Dos.name=Windows_NT</code> prior to invoking Ant has
- been confirmed as a workaround.</p>
- </answer>
- </faq>
-
- <faq id="1.5-cygwin-sh">
- <question>The <code>ant</code> wrapper script of Ant 1.5 fails
- for Cygwin if <code>ANT_HOME</code> is set to a Windows style
- path.</question>
- <answer>
-
- <p>This problem has been reported only hours after Ant 1.5 has
- been released, see <a
- href="http://issues.apache.org/bugzilla/show_bug.cgi?id=10664";>Bug
- 10664</a> and all its duplicates.</p>
-
- <p>A fixed version of the wrapper script can be found <a
- href="http://ant.apache.org/old-releases/v1.5/errata/";>here</a>.
- Simply replace your script with this version.</p>
- </answer>
- </faq>
-
- <faq id="1.5.2-zip-broken">
- <question><code><zip></code> is broken in Ant 1.5.2.</question>
- <answer>
-
- <p>Yes, it is.</p>
-
- <p>The problem reported by most people - see <a
- href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17648";>Bug
- 17648</a> and all its duplicates - is that Ant creates
- archives that a partially unreadable by WinZIP. Luckily
- <code>jar</code> deals with the archives and so the generated
- jars/wars/ears will most likely work for you anyway.</p>
-
- <p>There are additional problems, see bugs <a
- href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17780";>Bug
- 17780</a>, <a
- href="http://issues.apache.org/bugzilla/show_bug.cgi?id=17871";>Bug
- 17871</a> and <a
- href="http://issues.apache.org/bugzilla/show_bug.cgi?id=18403";>Bug
- 18403</a>. All of them are supposed to be fixed with Ant
- 1.5.3 (and only 18403 should exist in 1.5.3beta1).</p>
- </answer>
- </faq>
-
<faq id="unknownelement.taskcontainer">
<question>
Why do my custom task containers see Unknown Elements in Ant 1.6
@@ -1936,80 +1864,9 @@
</answer>
</faq>
- <faq id="java.exception.stacktrace">
- <question>
- The program I run via <java> throws an exception but I
- can't seem to get the full stack trace.
- </question>
- <answer>
- <p>This is a know bug that has been fixed after the release of
- Ant 1.6.1.</p>
-
- <p>As a workaround, run your <java> task with
- <code>fork="true"</code> and Ant will display the full
- trace.</p>
- </answer>
- </faq>
-
- <faq id="junit-no-runtime-xml">
- <question>
- Using format="xml", <junit> fails with a
- <code>NoClassDefFoundError</code> if forked.
- </question>
- <answer>
-
- <p>The XML formatter needs the <a
- href="http://www.w3.org/DOM/";>DOM classes</a> to work. If you
- are using JDK 1.4 or later they are included with your Java
- Runtime and this problem won't occur. If you are running JDK
- 1.3 or earlier, the DOM classes have to be on your
- <junit> task's <classpath>.</p>
-
- <p>Prior to Ant 1.6.0 Ant would include the DOM classes from
- the XML parser that is used by Ant itself if you set the
- includeAntRuntime attribute to true (the default). With Ant
- 1.6.0 this has been changed as this behavior made it
- impossible to use a different XML parser in your tests.</p>
-
- <p>This means that you have to take care of the DOM classes
- explicitly starting with Ant 1.6.0. If you don't need to set
- up a different XML parser for your tests, the easiest solution
- is to add</p>
-
- <source><![CDATA[
-<pathelement
path="${ant.home}/lib/xml-apis.jar:${ant.home}/lib/xercesImpl.jar"/>
-]]></source>
-
- <p>to your task's <classpath>.</p>
-
- </answer>
- </faq>
-
- <faq id="xalan-jdk1.5">
- <question>
- <code><junitreport></code> doesn't work with JDK 1.5 but
- worked fine with JDK 1.4.
- </question>
- <answer>
-
- <p>While JDK 1.4.x contains a version of Xalan-J 2, JDK 1.5
- (and later?) have <a
- href="http://java.sun.com/j2se/1.5.0/compatibility.html#4959783";>moved
- to XSLTC</a>. Since this task uses Xalan's redirect
- extensions for its internal stylesheet, Ant prior to 1.6.2 didn't
support
- XSLTC. This means that you have to install <a
- href="http://xml.apache.org/xalan-j/";>Xalan-J 2</a> in order
- to use this task with JDK 1.5 in older versions of Ant.</p>
-
- <p>Starting with Ant 1.6.2 <code><junitreport></code>
- supports JDK 1.5.</p>
-
- </answer>
- </faq>
-
<faq id="oom-on-mac">
<question>
- Ant runs into an infinite loop/throws an OutOufMemoryError
+ Ant runs into an infinite loop/throws an OutOfMemoryError
when I compile my project under Mac OS X.
</question>
