Repository navigation
LogcatAppender filtering #5
Description
Activity
- added a commit that references this issue
on Dec 31, 2011 Yes, that mostly satisfies my concern.
I do have a couple of questions, see the comments on the commit.This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
- locked as resolved and limited conversation to collaborators
on Feb 27, 2019
Not a bug, more user "gotcha".
The LogcatAppender is a wrapper around the android logger.
The android logger performs filtering using the system properties.
The issue is how the two filtering mechanism should interact.
Suppose there is a logger called "foo", the corresponding system
property has been set log.tag.foo DEBUG and the logback
config is filtering 'foo' to ERROR.
What should happen to, say, a WARN message?
My thought is that, if specified, the logback config should win
but there should be an unambiguous "pass" flag that
lets the underlying mechanism do its thing.