Or I could try to convert the timezone in the junitreport
but I'm not sure how do-able that would be in XSLT.
If you do it in the stylesheets, you don't need to alter JUnit java code.
This link shows the XSLT functions you need, and some examples:
http://www.xsltfunctions.com/xsl/fn_adjust-datet
You could use Ant's JUnitReport task just to create the consolidated xml
file (TESTS-TestSuites.xml),
and then call the XSLT task on that consolidated XML file.
You can than point the XSLT task's classpath(ref) attribute to your favorite
processor.
...
in="${b
If you are talking about running
ant test
, I have run them with JUnit4 on september 1 2006.
At that time, it ran 1500 tests, with 2 failures and 10 errors, without
blocking, in approx 1000 seconds.
I'm testing again with a fresh checkout..
Regards, Jan
- Original Message -
From: "P
Retested with fresh checkout,
Tested ok.
Total time: 18 minutes 7 seconds
Windows XP
Apache Ant version 1.7.0Beta2 compiled on October 6 2006
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)
Steve,
I just checked out the SVN head, and didn't have a problem building Ant:
BUILD SUCCESSFUL
Total time: 1 minute 45 seconds
C:\sandbox_ant\ant\ant-trunk>ant -version
Apache Ant version 1.7.0Beta3 compiled on October 23 2006
Environment:
Windows XP SP2
java version "1.5.0_06"
Regards, Jan
I'm looking for the problem that is resolved by commit r531340 .
This commit introduced two bugs,
http://issues.apache.org/bugzilla/show_bug.cgi?id=42227
http://issues.apache.org/bugzilla/show_bug.cgi?id=4
I'm trying to fix these bugs, but would like to know which failing usecase
was resolv
