[
https://issues.apache.org/jira/browse/TIKA-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Kautler updated TIKA-3727:
--------------------------------
Description:
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.
was:
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-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.
> 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)
