Don't obtrude a logging framework (conflicts)
I am using JXLS in my application as well as
org.slf4j. As SLF4Jimplementation we are using Log4j.
Since you are using another logging implementation, namely
ch.qos.logback:logback-classic:1.1.3, I get these errors by SLF4J:
SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/C:/Users/csh/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/C:/Users/csh/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.4.1/log4j-slf4j-impl-2.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
I am not sure, what I can do, that I can use Log4j (along with my logging configuration), but in general I am suggesting to only code against the SLF4J API and let users of your library decide which logging framework they want to use.
(I've seen you use
ch.qos.logback extensively in your code, so I am not sure this issue is feasible at all.)