Julian Hyde created CALCITE-3444:
------------------------------------
Summary: Upgrade SQLLine to 1.9.0, and solve "Class path contains
multiple SLF4J bindings" problem
Key: CALCITE-3444
URL: https://issues.apache.org/jira/browse/CALCITE-3444
Project: Calcite
Issue Type: Bug
Reporter: Julian Hyde
The "Class path contains multiple SLF4J bindings" is as follows:
{noformat}
sqlline version 1.9.0
sqlline> !connect jdbc:hsqldb:res:scott SCOTT TIGER
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/julianhyde/.m2/repository/org/slf4j/slf4j-log4j12/1.7.25/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/julianhyde/.m2/repository/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.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 [org.slf4j.impl.Log4jLoggerFactory]
0: jdbc:hsqldb:res:scott> {noformat}
Calcite's {{sqlline}} script generates {{target/fullclasspath.txt}} with both
of the above jar files on it. The solution is to remove one of them. I propose
to remove {{slf4j-log4j12}} from the generated classpath.
Windows uses a different technique (copying dependencies to each module's
target/dependencies directory). This change does not fix Windows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
