Why do tests show Log4j debug?

[Jason Dillon <ja...@planet57.com>]

Anyone know why (some) tests spit out Log4j debug messages like this:

<snip>
log4j: Parsing for [root] with value=[WARN, LOGFILE].
log4j: Level token is [WARN].
log4j: Category root set to WARN
log4j: Parsing appender named "LOGFILE".
log4j: Parsing layout options for "LOGFILE".
log4j: Setting property [dateFormat] to [ISO8601].
log4j: Setting property [contextPrinting] to [true].
log4j: End of parsing for "LOGFILE".
log4j: Setting property [maxBackupIndex] to [3].
log4j: Setting property [maxFileSize] to [10MB].
log4j: Setting property [file] to [scout.log].
log4j: setFile called: scout.log, true
log4j: setFile ended
log4j: Parsed "LOGFILE" options.
log4j: Parsing for [org.apache.axis.enterprise] with value=[FATAL,  
CONSOLE].
log4j: Level token is [FATAL].
log4j: Category org.apache.axis.enterprise set to FATAL
log4j: Parsing appender named "CONSOLE".
log4j: Parsing layout options for "CONSOLE".
log4j: Setting property [conversionPattern] to [- %m%n].
log4j: End of parsing for "CONSOLE".
log4j: Setting property [threshold] to [INFO].
log4j: Parsed "CONSOLE" options.
log4j: Handling log4j.additivity.org.apache.axis.enterprise=[null]
log4j: Finished configuring.
</snip>

I think we should remove this... as it is cluttering up the test  
output with... IMO rather useless information.

--jason