[
https://issues.apache.org/jira/browse/TIKA-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Isaac Haltom updated TIKA-4061:
--------------------------------------
Description:
The Automatic-Module-Name property for tika-parse-crypto-module.jar in
MANIFEST.MF is set to org.apache.tika.parser.code. This is the incorrect value.
This current blocks usage of Tika's Maven artifacts within IKVM projects. It
probably has ramifications for JDK9+ projects using modules as well, but that's
not me, so I don't know.
[https://github.com/ikvmnet/ikvm-maven/issues/33]
was:
The Automatic-Module-Name property for tika-parse-crypto-module.jar in
MANIFEST.MF is set to org.apache.tika.parser.code. This is the incorrect value.
This current blocks usage of Tika's Maven artifacts within IKVM projects.
https://github.com/ikvmnet/ikvm-maven/issues/33
> Incorrect Automatic-Module-Name in tika-parser-crypto-module
> ------------------------------------------------------------
>
> Key: TIKA-4061
> URL: https://issues.apache.org/jira/browse/TIKA-4061
> Project: Tika
> Issue Type: Bug
> Affects Versions: 2.8.0
> Reporter: Jerome Isaac Haltom
> Priority: Blocker
>
> The Automatic-Module-Name property for tika-parse-crypto-module.jar in
> MANIFEST.MF is set to org.apache.tika.parser.code. This is the incorrect
> value.
> This current blocks usage of Tika's Maven artifacts within IKVM projects. It
> probably has ramifications for JDK9+ projects using modules as well, but
> that's not me, so I don't know.
> [https://github.com/ikvmnet/ikvm-maven/issues/33]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
