Did anyone noticed a weird behavior of Xalan during unit tests report
generation. After I upgraded from JDK 1.4.0 to 1.4.1, any attempts to
generate reports from JUnit xml output would hang the build
indefinitely with 100% CPU consumption. Xalan seems to be bundled with
JDK now, I wonder if this is the cause of the problem? Interesting that
when instead of running all tests, I set a filter to run just one (that
generates a single .xml output file), Xalan report can be generated in
about 10 sec, but it totally chokes when there is many input files.
Ant file: build-tests.xml
Target: unit-test-report
OS: Mac OS X, Linux, Windows
Any ideas?
Andrus
This archive was generated by hypermail 2.0.0 : Sat Mar 29 2003 - 18:31:19 EST