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.

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 startup (adds them to the classpath) and sometimes the JAR files contain 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 the other logger implementations.