Geir Magnusson Jr. wrote:
... as suggested by Nikolay, I did run the tests
$ cd modules/logging
$ ant test
and it was endless stacktraces, both before and after I made the
modification.
How do I know if I broke anything? I'm going to go forward with the
patch as I don't see any harm, since Logger.global is supposed to be
set via getLogger("global") anyway, so subsequent settings shouldn't
harm.
"ant test" in specific module directory returns "build successfully"
even there is some tests fail, so I prefer to "ant
-Dbuild.module=logging test" in classlib/trunk directory, which will
check the test result and generate test report in html format.
About the logging tests, probably because of the default
java.util.logging.ErrorManager, wihch is used to handle the exception of
associated handlers, and its default behavior is to print the error
message to System.err, the solution I can imagine includes: redefine the
System.err to sth. like /dev/null, or specify a customized ErrorManager.
geir
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paulex Yang
China Software Development Lab
IBM
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
