[
https://issues.apache.org/jira/browse/TIKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282503#comment-17282503
]
Peter Kronenberg commented on TIKA-3297:
----------------------------------------
The use case for setting the paths at runtime is that I was actually thinking
of using my own env variables to set it. Because I might still have the same
problem of wanting to set it differently on multiple systems and I don't want
to dupliate the entire tika-config. Unless there is a way to combine multiple
tika-config files at runtime.
> 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)
