ebourg commented on pull request #381:
URL: https://github.com/apache/logging-log4j2/pull/381#issuecomment-653805579
I agree that `setLevel()` shouldn't throw an exception. It could maybe just
log a one time warning, but that's not worth breaking the application just
because log4j was plug
[
https://issues.apache.org/jira/browse/LOG4J2-2882?focusedWorklogId=454557&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-454557
]
ASF GitHub Bot logged work on LOG4J2-2882:
--
Author: ASF GitHub Bot
rgoers commented on pull request #381:
URL: https://github.com/apache/logging-log4j2/pull/381#issuecomment-653789389
Now that I look at this I find what was originally implemented rather odd.
The setLevel() and setParent() methods throw exceptions and yet the setFilter
method is still allo
[
https://issues.apache.org/jira/browse/LOG4J2-2882?focusedWorklogId=454543&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-454543
]
ASF GitHub Bot logged work on LOG4J2-2882:
--
Author: ASF GitHub Bot
carterkozak commented on pull request #367:
URL: https://github.com/apache/logging-log4j2/pull/367#issuecomment-653778469
This isn't something I had considered but it makes sense, thanks for the
contribution and for teaching me something new! I'll have to look into writing
an error-prone p
[
https://issues.apache.org/jira/browse/LOG4J2-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated LOG4J2-2882:
---
Environment: (was: {{monospaced text}})
> JUL adapter ignores log filters
>
