Providing a slf4j binding via provided-libs does not work

[cboehme]

From @cboehme on March 3, 2014 21:43

slf4j uses the same class loader which was used to load slf4j core to load the slf4j binding for a specific logging framework. In metafacture-runner these two packages are, however, loaded by different class loaders: the slf4j-api is loaded by the system default loader from the class path and the slf4j binding can be loaded only via DirectoryClassLoader from the provided-libs directory. As a result slf4j fails to load a binding.

At the moment, the only feasible solution for this problem seems to be to put the slf4j binding also on the class path at the expense of preventing the user from changing the logging framework.

Copied from original issue: culturegraph/metafacture-runner#2