You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2022/04/21 17:14:00 UTC
[jira] [Commented] (TIKA-3727) Do not depend on JCL implementations
[ https://issues.apache.org/jira/browse/TIKA-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525862#comment-17525862 ]
Tim Allison commented on TIKA-3727:
-----------------------------------
I'm removing it now from tika-standard-parsers-package. Thank you for opening this issue.
We'll still have it in tika-app, tika-server-core, tika-bundle and tika-parser-scientific-module via our own dependencies or transitive dependencies.
That ok?
> Do not depend on JCL implementations
> ------------------------------------
>
> Key: TIKA-3727
> URL: https://issues.apache.org/jira/browse/TIKA-3727
> Project: Tika
> Issue Type: Bug
> Affects Versions: 2.3.0
> Reporter: Björn Kautler
> Priority: Major
>
> Similar to TIKA-3535 tika should not depend on any JCL implementations as this might downstream conflict with other implementations.
> {{org.apache.tika:tika-parsers-standard-package:2.3.0}} depends on {{jcl-over-slf4j}} which is a JCL implementation forwarding to SLF4J.
> But if a downstream project for example has {{log4j-jcl}}, you suddenly have two JCL implementations.
> The tika projects should not depend on any logging implementations or bridges.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)