[
https://issues.apache.org/jira/browse/TIKA-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770591#comment-17770591
]
Hudson commented on TIKA-4135:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk11 #1313 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1313/])
TIKA-4135 -- can't rely on English-only messages from Java xml parsers now that
we've removed xerces (tallison:
[https://github.com/apache/tika/commit/20e17f2971c62a76091754914ad633560691f695])
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/parser/TestXMLEntityExpansion.java
> Remove xerces from Tika 3.x/main branch?
> ----------------------------------------
>
> Key: TIKA-4135
> URL: https://issues.apache.org/jira/browse/TIKA-4135
> Project: Tika
> Issue Type: Wish
> Reporter: Tim Allison
> Priority: Major
>
> We've gotten requests over the years to get rid of xerces. Should we do that
> in 3.x/main?
> The one nice thing about including it is that it offers some consistency
> across java versions and platforms. This can help with securing the parsers
> (against xxe, etc). This can also make debugging easier.
> However, as people have pointed out, the xerces project appears to be in
> security-fix-only mode.
> WDYT?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
