[
https://issues.apache.org/jira/browse/TIKA-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989907#comment-16989907
]
Nick Burch commented on TIKA-2929:
----------------------------------
At the moment, Apache Tika needs to be on the Java Classpath, not the module
path.
It's probably unlikely that Tika 1.x will ever work on the module path. It is
possible that Tika 2.x could, with the modularisation work underway. However,
that would need volunteers to help, and especially to help many of the
maintainers of our dependencies with their necessary changes
(For more on the challenges for long-standing Java libraries and the Java 11
module path stuff, I can suggest https://www.youtube.com/watch?v=Ipe-2h1MKKs
from ApacheCon EU 2019)
> tika-parsers not usable on module path (Java 11)
> ------------------------------------------------
>
> Key: TIKA-2929
> URL: https://issues.apache.org/jira/browse/TIKA-2929
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.22
> Reporter: Tobias Diez
> Priority: Major
>
> At the moment, it is not possible to use tika-parsers in a modularized
> environment. The following error is thrown at runtime:
> java.lang.module.FindException: Unable to derive module descriptor for
> org.apache.tika\tika-parsers\1.22\b8a823128f6165882ae41de3ded8655609d62d88\tika-parsers-1.22.jar
> Caused by: java.lang.module.InvalidModuleDescriptorException: Provider class
> org.apache.tika.parser.external.CompositeExternalParser not in module
>
> Could you please provide a proper module-info.java class listing the
> necessary providers (and dependencies of course).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
