The following components depend on hadoop-common (package hadoop) and thus get slf4j JARs twice on their classpath (once as a second-level dependency of hadoop-common and second time from their own lib):
This leads to the harmless, but very annoying "Class path contains multiple SLF4J bindings" warning message to pop up.
Now, this is not a new problem for us – unfortunately we tend to have multiple instances of the same JARs in the Bigtop's classpath quite a bit. As such one way of "fixing" it would be just making slf4j shut up. The other alternative is to remove slf4j jar files from all the packages mentioned above. This is pretty good, expect for an off chance that somehow the component could be used in a standalone mode
where it can't really find hadoop. Not sure how important such a use case would be.