[
https://issues.apache.org/jira/browse/TIKA-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619365#comment-14619365
]
Ken Krugler commented on TIKA-1675:
-----------------------------------
Not sure why the above discussion is being classified as "political".
As Uwe points out, this would best be solved by POI, since it's their
dependency that's causing the problem.
If they can't or won't fix it fast enough, then the fallback solution would be
for us (Tika) to fix up the xmlbeans jar (e.g. as per
https://issues.apache.org/jira/browse/XMLBEANS-499?focusedCommentId=14258877&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14258877),
push it with a new version to Maven central, and then edit our pom to override
the version used by POI.
Or is there another, better way in Tika to work around the problem?
> please avoid xmlbeans dependency
> --------------------------------
>
> Key: TIKA-1675
> URL: https://issues.apache.org/jira/browse/TIKA-1675
> Project: Tika
> Issue Type: Bug
> Reporter: Robert Muir
>
> This dependency (e.g jar file) is fundamentally broken... XMLBEANS-499
> Is there an alternative that could be used?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
