[
https://issues.apache.org/jira/browse/TIKA-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932645#comment-17932645
]
Tim Allison commented on TIKA-4392:
-----------------------------------
Thank you for opening this. We definitely need to fix this. I'm wondering if we
just finish tearing out the xerces stuff entirely with a warning that if xerces
is on your classpath, security is your responsibility?
> 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
>
>
> *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)
