diff --git a/docs/faq.html b/docs/faq.html index fbb0c7f7a..eea3d5751 100644 --- a/docs/faq.html +++ b/docs/faq.html @@ -407,9 +407,6 @@
  • <chmod> or <exec> doesn't work in Ant 1.3 on Unix -
    • -
  • - JavaDoc failed: java.io.IOException: javadoc: cannot execute
  • <style> or <junit> ignores my @@ -422,48 +419,16 @@
  • <style> or <junit> ignores my <classpath> - Ant 1.6.x version -
    • -
  • - 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. -
    • -
  • - The ant wrapper script of Ant 1.5 fails - for Cygwin if ANT_HOME is set to a Windows style - path. -
    • -
  • - <zip> is broken in Ant 1.5.2.
  • Why do my custom task containers see Unknown Elements in Ant 1.6 - they worked in Ant 1.5? -
    • -
  • - - The program I run via <java> throws an exception but I - can't seem to get the full stack trace. - -
    • -
  • - - Using format="xml", <junit> fails with a - NoClassDefFoundError if forked. - -
    • -
  • - - <junitreport> doesn't work with JDK 1.5 but - worked fine with JDK 1.4. -
  • - 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.
    • @@ -1924,14 +1889,6 @@ tr -d '\r' < $ANT_HOME/bin/antRun > /tmp/foo 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> @@ -2138,48 +2095,6 @@ mv /tmp/foo $ANT_HOME/bin/antRun </taskdef>

    - - 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 @@ -2229,61 +2144,9 @@ mv /tmp/foo $ANT_HOME/bin/antRun This approach should work for ant1.5 and ant1.6.

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

    - 
    -<pathelement path="${ant.home}/lib/xml-apis.jar:${ant.home}/lib/xercesImpl.jar"/>
-
    -

    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.