diff --git a/docs/manual/OptionalTasks/junit.html b/docs/manual/OptionalTasks/junit.html index a89b92b37..646fbe93f 100644 --- a/docs/manual/OptionalTasks/junit.html +++ b/docs/manual/OptionalTasks/junit.html @@ -183,10 +183,7 @@ elements).

includeantruntime Implicitly add the Ant classes required to run the tests and JUnit to the classpath in forked mode. - Note: Please read the Ant FAQ if you - want to set this to false and use the XML formatter - at the same time. + No; default is true. @@ -379,12 +376,6 @@ failing methods. The name and the location can be specified via Java System prop ant.junit.failureCollector. The value has to point to the directory and the name of the resulting class (without suffix). It defaults to java-tmp-dir/FailedTests.

-

Note: Please read the Ant FAQ if you want to -set the fork attribute to true, the includeAntRuntime -attribute to false and use the XML formatter at the same -time.

- diff --git a/xdocs/faq.xml b/xdocs/faq.xml index d7e5e29ea..941016bfa 100644 --- a/xdocs/faq.xml +++ b/xdocs/faq.xml @@ -1566,16 +1566,6 @@ mv /tmp/foo $ANT_HOME/bin/antRun - - JavaDoc failed: java.io.IOException: javadoc: cannot execute - -

There is a bug in the Solaris reference implementation of - the JDK (see http://developer.java.sun.com/developer/bugParade/bugs/4230399.html). - This also appears to be true under Linux. Moving the JDK to - the front of the PATH fixes the problem.

- - - <style> or <junit> ignores my <classpath> @@ -1823,68 +1813,6 @@ mv /tmp/foo $ANT_HOME/bin/antRun - - When running Ant 1.4 on Windows XP and JDK 1.4, I get - various errors when trying to <exec>, fork - <java> or access environment - variables. - - - -

Ant < 1.5 doesn't recognize Windows XP as a flavor - of Windows that runs CMD.EXE instead of - COMMAND.COM. JDK 1.3 will tell Ant that Windows - XP is Windows 2000 so the problem doesn't show up - there.

- -

Apart from upgrading to Ant 1.5 or better, setting the - environment variable ANT_OPTS to - -Dos.name=Windows_NT prior to invoking Ant has - been confirmed as a workaround.

- - - - - The ant wrapper script of Ant 1.5 fails - for Cygwin if ANT_HOME is set to a Windows style - path. - - -

This problem has been reported only hours after Ant 1.5 has - been released, see Bug - 10664 and all its duplicates.

- -

A fixed version of the wrapper script can be found here. - Simply replace your script with this version.

- - - - - <zip> is broken in Ant 1.5.2. - - -

Yes, it is.

- -

The problem reported by most people - see Bug - 17648 and all its duplicates - is that Ant creates - archives that a partially unreadable by WinZIP. Luckily - jar deals with the archives and so the generated - jars/wars/ears will most likely work for you anyway.

- -

There are additional problems, see bugs Bug - 17780, Bug - 17871 and Bug - 18403. All of them are supposed to be fixed with Ant - 1.5.3 (and only 18403 should exist in 1.5.3beta1).

- - - Why do my custom task containers see Unknown Elements in Ant 1.6 @@ -1936,80 +1864,9 @@ mv /tmp/foo $ANT_HOME/bin/antRun - - - The program I run via <java> throws an exception but I - can't seem to get the full stack trace. - - -

This is a know bug that has been fixed after the release of - Ant 1.6.1.

- -

As a workaround, run your <java> task with - fork="true" and Ant will display the full - trace.

- - - - - - Using format="xml", <junit> fails with a - NoClassDefFoundError if forked. - - - -

The XML formatter needs the DOM classes 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>.

- -

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.

- -

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

- - -]]> - -

to your task's <classpath>.

- - - - - - - <junitreport> doesn't work with JDK 1.5 but - worked fine with JDK 1.4. - - - -

While JDK 1.4.x contains a version of Xalan-J 2, JDK 1.5 - (and later?) have moved - to XSLTC. 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 Xalan-J 2 in order - to use this task with JDK 1.5 in older versions of Ant.

- -

Starting with Ant 1.6.2 <junitreport> - supports JDK 1.5.

- - - - - 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.
Attribute