-
Improvement
-
Resolution: Fixed
-
Trivial
-
None
-
None
In some tests, irrelevant loggers are pretty verbose. eg when using slf4j-simple and extending RepositoryTestCase, we get a ton of Jackrabbit logging that isn't necessarily helpful.
In several tests of core, we already do this
// Silence log4j completely
org.apache.log4j.Logger.getRootLogger().setLevel(org.apache.log4j.Level.OFF);
or this
// Silence log4j for a specific category
org.apache.log4j.Logger.getLogger(org.apache.commons.digester.Digester.class).setLevel(org.apache.log4j.Level.OFF);
This adds a simple method in TestUtil which does this for both log4j and slf4j-simple.
Acceptance criteria