[
https://issues.apache.org/jira/browse/TIKA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321960#comment-17321960
]
Arnaud MERGEY commented on TIKA-3354:
-------------------------------------
digging more about this I think I found the explanation:
[https://stackoverflow.com/questions/45855091/maven-bundle-plugin-generates-manifest-with-wrong-or-missing-versions]
In my case I have the bundle commons-io from eclipse orbit which exports
packages with its own version (which is v2) instead of 1.4 as apache regular
jar is doing.
The fix to this is probably to "force" org.apache.commons.io.output with a
range in [1.4,3) in maven-bundle-plugin instructions
> [tika-parsers] Wrong commons-io version imported
> ------------------------------------------------
>
> Key: TIKA-3354
> URL: https://issues.apache.org/jira/browse/TIKA-3354
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 1.26
> Reporter: Arnaud MERGEY
> Priority: Major
>
> tika-parsers is not importing the correct commons-io version in osgi.
> Manifest is importing commons io 1
> {code:java}
> org.apache.commons.io.output;resolution:=optional;version="[1.4,2)"{code}
> it should import version 2.8 of commons io as declared in maven
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
