[ https://issues.apache.org/jira/browse/TIKA-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769974#comment-17769974 ]
Tim Allison commented on TIKA-4139: ----------------------------------- >Shall I create new JIRA? Yes, please! >Maybe I can write some bash script Ha, I can do that too. LOL.... Relatedly, if you can find any other split packages that we should fix in 3.x, please let us know. > Tika modules are not JPMS friendly > ---------------------------------- > > Key: TIKA-4139 > URL: https://issues.apache.org/jira/browse/TIKA-4139 > Project: Tika > Issue Type: Improvement > Affects Versions: 2.9.0 > Reporter: Maxim Solodovnik > Priority: Major > Fix For: 3.0.0-BETA > > > Hello, > Tika-3 has some major changes, let's add some more :) > Recently I got following warning while trying to use Tika in JPMS web > application: > {code} > [INFO] --- compiler:3.11.0:compile (default-compile) @ openmeetings-util --- > [WARNING] Can't extract module name from > tika-parsers-standard-package-2.9.0.jar: tika.parsers.standard.package: > Invalid module name: 'package' is not a Java identifier > {code} > I've checked {code}main{code} branch and find no {{module-info.java}} and > {{Automatic-Module-Name}} also doesn't set. > Maybe {{Automatic-Module-Name}} can be added to Tika modules? -- This message was sent by Atlassian Jira (v8.20.10#820010)