[ https://jira.qos.ch/browse/SLF4J-373?page=com.atlassian.jira.plugin.system.i... ] Jeremy Landis commented on SLF4J-373: ------------------------------------- I would close this too.  It's not a bug.  Do you want to log to log4j 1.2 or jdk 1.4?  You have to pick one and the link tells you why.  So in your case, exclude one of them.  If this is due to some classloading issue in EAR where those are in different WARs, while I cannot help much I would ask why are you still using EARs to start with?  Almost every EAR I've ran into in my development career has been incorrectly used and completely unnecessary and with microservices all the rage, there is really no compelling reason to use them.  But if you must, there are ways to fix the issue you see without having a fix to this library.

SLF4J: Class path contains multiple SLF4J bindings --------------------------------------------------

Key: SLF4J-373 URL: https://jira.qos.ch/browse/SLF4J-373 Project: SLF4J Issue Type: Bug Components: Unspecified Affects Versions: 1.7.x Reporter: Pu Yi He Assignee: SLF4J developers list

In our project, there is one warning message as below when to use slf4j-1.7.5, how to resolve this issue? - project dependency: <dependency name="slf4j-1.7.5" type="jar" version="1.7.5"/> this will include slf4j-api-1.7.5.jar and slf4j-log4j12-1.7.5.jar <dependency name="hystrix" type="jar" /> this will include slf4j-api-1.7.5.jar and slf4j-jdk14-1.7.5.jar - warning message: WARNING: Couldn't load build resource bundle. Build timestamp will be inaccurate *** SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [wsjar:file:/xxx.ear/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [wsjar:file:/xxx.ear/slf4j-jdk14-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]* SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

-- This message was sent by Atlassian JIRA (v7.3.1#73012)