This is actually a bug [1] that will be fixed in the next release. Thanks for bringing it to my attention ;) The first line of your output is a warning that logback couldn't find a configuration file in the SD card at the designated path. Initialization is normally silent unless a debug flag is asserted in the config/environment; or a warning/error occurred during configuration -- you're seeing the latter. [1] https://github.com/tony19/logback-android/issues/27 On Tue, Oct 30, 2012 at 12:10 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
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@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@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@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@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-... Sent from the Logback User mailing list archive at Nabble.com.
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user