You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2025/09/24 18:39:00 UTC

[jira] [Resolved] (TIKA-4392) Incorrect "org.apache.xerces.util"-entry in Manifest file

     [ https://issues.apache.org/jira/browse/TIKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-4392.
-------------------------------
    Fix Version/s: 4.0.0
                   3.3.0
       Resolution: Fixed

> Incorrect "org.apache.xerces.util"-entry in Manifest file
> ---------------------------------------------------------
>
>                 Key: TIKA-4392
>                 URL: https://issues.apache.org/jira/browse/TIKA-4392
>             Project: Tika
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Steven Huypens
>            Priority: Major
>             Fix For: 4.0.0, 3.3.0
>
>
>  
> *Issue:* The {{tika-core}} Manifest file has an {{Import-Package}} entry for {{{}org.apache.xerces.util{}}}, which necessitates provisioning a Xerces library with our OSGi application (which I'd prefer to avoid).
> *Details:* Since TIKA-4135, Tika only uses the Xerces package {{org.apache.xerces.util}} in one place. As this usage is via reflection and the {{ClassNotFoundException}} is caught, the Xerces dependency is not strictly necessary, so the {{Import-Package}} should not be generated.
> *Solution:* Add {{!org.apache.xerces.util}} to the {{Import-Packages}} entry in the {{tika-core}} {{{}pom.xml{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)