[logback-user] logback-android: How to suppress bootstrap messages?

cowwoc cowwoc at bbs.darktech.org
Tue Oct 30 18:10:11 CET 2012


Hi,

When I launch an application using logback-android I get the following logs
at startup:

10-30 13:03:41.341: I/System.out(1022): 13:03:39,311 |-WARN in
ch.qos.logback.classic.LoggerContext[default] - No config in SD card
10-30 13:03:41.341: I/System.out(1022): 13:03:39,314 |-INFO in
ch.qos.logback.classic.LoggerContext[default] - Found resource
[AndroidManifest.xml] at
[jar:file:/data/app/com.foo-1.apk!/AndroidManifest.xml]
10-30 13:03:41.341: I/System.out(1022): 13:03:40,178 |-INFO in
ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource
[assets/logback-test.xml]
10-30 13:03:41.341: I/System.out(1022): 13:03:40,179 |-INFO in
ch.qos.logback.classic.LoggerContext[default] - Found resource
[assets/logback.xml] at
[jar:file:/data/app/com.foo-1.apk!/assets/logback.xml]
10-30 13:03:41.341: I/System.out(1022): 13:03:40,182 |-INFO in
ch.qos.logback.core.joran.spi.ConfigurationWatchList at 411f2f88 - URL
[jar:file:/data/app/com.foo-1.apk!/assets/logback.xml] is not of type file
10-30 13:03:41.341: I/System.out(1022): 13:03:41,072 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute
not set
10-30 13:03:41.341: I/System.out(1022): 13:03:41,072 |-INFO in
ch.qos.logback.core.joran.action.AppenderAction - About to instantiate
appender of type [ch.qos.logback.classic.android.LogcatAppender]
10-30 13:03:41.341: I/System.out(1022): 13:03:41,073 |-INFO in
ch.qos.logback.core.joran.action.AppenderAction - Naming appender as
[logcat]
10-30 13:03:41.341: I/System.out(1022): 13:03:41,091 |-INFO in
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default
type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder]
property
10-30 13:03:41.341: I/System.out(1022): 13:03:41,245 |-INFO in
ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding
LoggerContextListener of type
[ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
10-30 13:03:41.341: I/System.out(1022): 13:03:41,246 |-INFO in
ch.qos.logback.classic.jul.LevelChangePropagator at 4123c198 - Propagating
DEBUG level on Logger[ROOT] onto the JUL framework
10-30 13:03:41.341: I/System.out(1022): 13:03:41,247 |-INFO in
ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting
LoggerContextListener
10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in
ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT
logger to WARN
10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in
ch.qos.logback.classic.jul.LevelChangePropagator at 4123c198 - Propagating WARN
level on Logger[ROOT] onto the JUL framework
10-30 13:03:41.351: I/System.out(1022): 13:03:41,247 |-INFO in
ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender
named [logcat] to Logger[ROOT]
10-30 13:03:41.351: I/System.out(1022): 13:03:41,248 |-INFO in
ch.qos.logback.classic.joran.action.ConfigurationAction - End of
configuration.
10-30 13:03:41.351: I/System.out(1022): 13:03:41,249 |-INFO in
ch.qos.logback.classic.joran.JoranConfigurator at 4127e938 - Registering
current configuration as safe fallback point

Is there a way to suppress these logs unless a configuration problem is
encountered?

Thanks,
Gili
-- 
View this message in context: http://old.nabble.com/logback-android%3A-How-to-suppress-bootstrap-messages--tp34620687p34620687.html
Sent from the Logback User mailing list archive at Nabble.com.



More information about the Logback-user mailing list