![]() It is also important to note that this is only a warning. So, they should only depend on the slf4j-api library. Obviously, this negates SLF4J's basic purpose. This is because when a library declares a compile-time dependency on an SLF4J binding, it imposes that binding on the end user. It is worth noting that embedded components such as libraries or frameworks should never declare a dependency on any SLF4J binding. Consequently, if more than one binding is present on the classpath, it will emit a warning. Bindings are basically implementations of a particular SLF4J class meant to be extended to plug in a specific logging framework.īy design, SLF4J will only bind with one logging framework at a time. To achieve this, SLF4J looks for bindings (aka providers) on the classpath. It allows us to plug in our desired logging framework at deployment time. The Simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks.
0 Comments
Leave a Reply. |