This is a HBase shell nit specifically, and the warning from SLF4J is
purely a warning:
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/usr/lib/hadoop/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/lib/zookeeper/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for
an explanation.
but there are other cases where dependencies in common to more than
one project will appear on the classpath, sometimes with differing
versions. Jackson comes to mind.
How this would be handled at the OS level is each common dependency
would be factored out into a library package.
Is there something under consideration for Bigtop for issues like this?
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet
Hein (via Tom White)
