Hi, folks. I'm currently refactoring 2.x branch to unify logging there [1].
Did we relaxed our policy about deps in tika-core? As I see there are commons-io and commons-codec in its deps. I do remember discussions about commons-io but not about commons-codec. What about adding org.slf4j:slf4j-api also? It's not a big dependency and simplifies logging configuration for user. JUL has no way to bridge to SLF4J automatically I'm aware of. Without additional downstream code, I mean. To forward JUL to SLF4J you have to add jul-to-slf4j as dependecy *and* invoke static method in SLF4JBridgeHandler to register it. It forces downstream user to write additional code to make logging work as intended. Almost everyone use some dependency management tool (Maven/Ant+Ivy/Gradle/SBT/whatever) in their projects, so it shouldn't be something bothersome for end user. What do you think, folks? [1]: https://issues.apache.org/jira/browse/TIKA-2314 -- Best regards, Konstantin Gribov
