[slf4j-dev] [JIRA] Updates for SLF4J-505: Ignore Multiple Bindings Warning
QOS.CH (JIRA)
noreply-jira at qos.ch
Sat Jan 16 15:38:00 CET 2021
SLF4J / SLF4J-505 [Open]
Ignore Multiple Bindings Warning
==============================
Here's what changed in this issue in the last few minutes.
This issue has been created
This issue is now assigned to you.
View or comment on issue using this link
https://jira.qos.ch/browse/SLF4J-505
==============================
Issue created
------------------------------
DAVID MOLLITOR created this issue on 16/Jan/21 3:27 PM
Summary: Ignore Multiple Bindings Warning
Issue Type: Improvement
Assignee: SLF4J developers list
Created: 16/Jan/21 3:27 PM
Priority: Major
Reporter: DAVID MOLLITOR
Description:
{quote}SLF4J API is designed to bind with one and only one underlying logging framework at a time. If more than one binding is present on the class path, SLF4J will emit a warning, listing the location of those bindings.
The warning emitted by SLF4J is just that, a warning.
{quote}
Please add a command-line option {{-D}} to silence this particular warning in regards to _multiple bindings were found on the class path_.
I have a command-line tool that loads JAR files (including uber JARs) at runtime and sometimes the JAR files contains an SLF4J logger implementation. It is annoying and scary for users to see this warning when they run this command line tool. I understand that these are just warnings, and that it does not affect the operation of the tool, but I would like a way to "acknowledge" these warnings so that they are not printed at all. Since these JARs are loaded at run-time, it is not possible to change the POM/Graddle files to exclude them.
==============================
This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)
More information about the slf4j-dev
mailing list