[ https://jira.qos.ch/browse/SLF4J-314?page=com.atlassian.jira.plugin.system.i... ] Mike Mitterer commented on SLF4J-314: ------------------------------------- Guys, [~nitin_matrix] this is a bug! If I want debug output the slf4j should give me what I want. Androids TAG-based approach is crap. This is how I set my logger: private static Logger logger = LoggerFactory.getLogger(Connection.class); setprop fails because it tells me that my name for the full class is to long. [~vyzivus] is approach is much better!
slf4j not logging VERBOSE and DEBUG messages, no matter what is Logcat's loglevel ---------------------------------------------------------------------------------
Key: SLF4J-314 URL: https://jira.qos.ch/browse/SLF4J-314 Project: SLF4J Issue Type: Bug Components: slf4j-android Affects Versions: 1.7.x Environment: Operating System: All Platform: Other Reporter: Mark Zalavari Assignee: SLF4J developers list
It seems on android platform the isLoggable() method is always returns false for VERBOSE and DEBUG (no matter what is the actal loglevel is), so it should not be called before calling Log.d and Log.v The only slf4j version I know of where the DEBUG & VERBOSE logs are working is 1.6.1-RC1
-- This message was sent by Atlassian JIRA (v7.3.1#73012)