[
https://issues.apache.org/jira/browse/TIKA-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531945#comment-17531945
]
Hudson commented on TIKA-3750:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #542 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/542/])
TIKA-3750 - Fixed bug in ordering of Parsers during service loading. (tallison:
[https://github.com/apache/tika/commit/42da02ef1b8d1641b7bef3a3aa016fbcc6f40b9d])
* (edit) tika-core/src/main/java/org/apache/tika/parser/DefaultParser.java
* (edit) CHANGES.txt
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-package/src/test/java/org/apache/tika/utils/ServiceLoaderUtilsTest.java
> Bug in sorting parsers
> ----------------------
>
> Key: TIKA-3750
> URL: https://issues.apache.org/jira/browse/TIKA-3750
> Project: Tika
> Issue Type: Bug
> Reporter: Tim Allison
> Priority: Major
> Fix For: 2.4.1
>
>
> Throughout our documentation and unit tests, we declare that parsers with a
> different namespace than org.apache.tika should come first. The problem is
> that the DefaultParser iterates through the list of parsers and overwrites
> parsers based on supported mime types.
> So, if there's a custom parser {{com.acme.parser.PDFParser}} that supports
> {{application/pdf}}, that will be added to the map of parsers in
> DefaultParser first and then overwritten by org.apache.tika's PDFParser.
> We should instead sort non-o.a.t. parsers last, no?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
