[
https://issues.apache.org/jira/browse/TIKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282596#comment-17282596
]
Hudson commented on TIKA-3297:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #156 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/156/])
TIKA-3297 -- prevent loading of parsers and detectors that are excluded
(tallison:
[https://github.com/apache/tika/commit/73ead01b1d2c8aa89fffc1ee048a832d1b84e9a2])
* (edit) tika-core/src/main/java/org/apache/tika/detect/DefaultDetector.java
* (edit) tika-core/src/test/java/org/apache/tika/parser/mock/MockParser.java
* (edit) tika-core/src/main/java/org/apache/tika/parser/DefaultParser.java
* (edit) tika-core/src/test/java/org/apache/tika/config/TikaConfigTest.java
* (edit) tika-core/src/main/java/org/apache/tika/config/ServiceLoader.java
* (add) tika-core/src/test/resources/org/apache/tika/config/mock-exclude.xml
> Simplify parser configuration in 2.x
> ------------------------------------
>
> Key: TIKA-3297
> URL: https://issues.apache.org/jira/browse/TIKA-3297
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0
>
>
> We currently have .properties files and tika-config.xml and runtime
> configuration. We should simplify to tika-config.xml.
> From a security perspective, I'm thinking we should also allow executable
> paths to be set only via tika-config.xml...not programmatically via a
> TesseractConfig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
