[
https://issues.apache.org/jira/browse/TIKA-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562894#comment-17562894
]
Josh Burchard commented on TIKA-3293:
-------------------------------------
[~tilman] I'm guessing this was possibly fixed indirectly with some other
commit. I'm seeing this exact stack on the IBM i / OS400 platform. I'm
calling TikaServerCli and I'd rather not have to pass the -noFork option to use
1.x style single process. Any idea what the fix was for this? (or [~tallison]
, do you know?)
> Move most commandline options for tika-server into a config file in 2.0.0
> -------------------------------------------------------------------------
>
> Key: TIKA-3293
> URL: https://issues.apache.org/jira/browse/TIKA-3293
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> We now have a huge amount of commandline options for tika-server. I propose
> moving them into a config file. Given that TikaConfig doesn't mind elements
> that it isn't looking for, we can add this to a tika-config.xml file.
>
> I tried to extend TikaConfig, and it was, um, non-trivial. So, this proposal
> would have tika-server and tikaconfig reading the same file twice and looking
> for different elements.
>
> Any objections?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
