This is an important point - most of the Xalan tests simply do a logHashtable() of System.getProperties, as well as logging any testProps on the test itself. Having the test (or some bit of the framework) log out the properties used in the actual test itself is very useful for debugging.
This is especially useful to catch both java.exe differences (as noted below) as well as classpath ordering issues, especially with JDK 1.2+ versions with various XML-related jars in the special ext directory. Took a while to figure those out, and will become more of a runtime issue when future JDK's come out that include more and more default 'extension' libraries like parsers, processors, DOM and SAX interfaces, etc. get 'magically' stuck into your classpath... - Shane ---- you "Stephane Bailliez" <[EMAIL PROTECTED]> wrote ---- > However, We should pay attention to this, since the JVM info are not > necessarily the JVM info used to run the testcases (depends if fork is > enabled or not and if your java exe in your path match the one used to run > ant via JAVA_HOME.) > > Windows users often have some nice surprises since the JRE exes are copied > into system32 and that this is the first in the path. Personnally, i'm > wiping out these exe to avoid confusion. This is also why these info should > definitely be part of the testcase reports in order to be sure how tests > were run.
