You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2023/06/10 18:26:00 UTC

[jira] [Commented] (TIKA-4061) Incorrect Automatic-Module-Name in tika-parser-crypto-module

    [ https://issues.apache.org/jira/browse/TIKA-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731242#comment-17731242 ] 

Hudson commented on TIKA-4061:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1103 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1103/])
TIKA-4061 -- incorrect automatic module name in crypto parser module (tallison: [https://github.com/apache/tika/commit/710d972ee1278e347b02527269050df727ee7ce8])
* (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-crypto-module/pom.xml


> 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
>            Assignee: Tim Allison
>            Priority: Blocker
>             Fix For: 2.8.1
>
>
> 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)