[
https://issues.apache.org/jira/browse/TIKA-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445471#comment-17445471
]
Bob Paulin commented on TIKA-3591:
----------------------------------
Hey [~tallison] . The commons-io library is what's saying hey you can use 1.4
if you'd like [1]. So even though you're saying use 2.11.0 commons-io is
going to export those packages with the 1.4 version. So I don't think it's
wrong that tika-core imports 1.4 in this case since that's what commons-io is
telling it to do. I think the trouble is with the tika-bundle-standard. If
the commons-io classes are embedded in the bundle it should NOT need to import
it as it is instructed to do [2]. I'd suggest removing that line rather than
explicitly setting the versions. Having the jar embedded AND importing those
packages can lead to unpredictable results based on the runtime.
[1][https://github.com/apache/commons-io/blob/884e5ecee572856804a2303e0bb53ab15f1a7543/pom.xml#L320]
[2]
[https://github.com/apache/tika/blob/f750410ce5ec206acca156a71de6b32396a78416/tika-bundles/tika-bundle-standard/pom.xml#L222]
> The Import-Package of commons.io is wrong in MANIFEST.MF
> --------------------------------------------------------
>
> Key: TIKA-3591
> URL: https://issues.apache.org/jira/browse/TIKA-3591
> Project: Tika
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Per Kristian Söreide
> Priority: Major
>
> The tika-bundle-standard bundle get version 1.4 of commons.io which leads to
> NoSuchMethodException in some Parsers/Detectors since they require later
> versions of commons.io.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
