Hi all, Am I the only one who is bothered by the verbose unit test output? Running maven test (or even maven jar!) results in lots of debug messages being printed. The same messages are also stored in the jcr.log file.
Would it be bad if the default logging configuration was changed? Having less of the useless clutter helps to identify test failures and other problems. The patch below cleans up the unit test output. OK to commit? BR, Jukka Zitting Index: applications/test/log4j.properties =================================================================== --- applications/test/log4j.properties (revision 156417) +++ applications/test/log4j.properties (working copy) @@ -1,7 +1,7 @@ # Set root logger level to DEBUG and its only appender to A1. -log4j.rootLogger=INFO, stdout, file -#log4j.rootLogger=DEBUG, stdout, file -#log4j.rootLogger=ERROR, stdout, file +log4j.rootLogger=INFO, file +#log4j.rootLogger=DEBUG, file +#log4j.rootLogger=ERROR, file log4j.logger.org.apache.jackrabbit.test=DEBUG
