SLF4J does not rely on any special class loader machinery. In fact, each SLF4J binding is hardwired at compile time to use one and only one specific logging framework. For example, the slf4j-log4j12-2.0.6.jar binding is bound at compile time to use log4j. In your code, in addition to slf4j-api-2.0.6.jar, you simply drop one and only one binding of your choice onto the appropriate class path location. Do not place more than one binding on your class path.
windows loader 2.0.6 download
2ff7e9595c
Comments