[
https://issues.apache.org/jira/browse/TIKA-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-3589.
-------------------------------
Fix Version/s: 2.1.1
Assignee: Tim Allison
Resolution: Fixed
> Two trivial bugs in tika-app's commandline interpretation for tika-batch
> ------------------------------------------------------------------------
>
> Key: TIKA-3589
> URL: https://issues.apache.org/jira/browse/TIKA-3589
> Project: Tika
> Issue Type: Bug
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 2.1.1
>
>
> In a private message [~kkrugler] pointed out that log4j2 was not being
> correctly configured in tika-app when running in batch mode:
> {noformat} INFO [Thread-1] 13:23:32,119
> org.apache.tika.batch.BatchProcessDriverCLI BatchProcess: ERROR StatusLogger
> Reconfiguration failed: No configuration found for '4b85612c' at 'null' in
> 'null'{noformat}
> Separately, I noticed that {{--config=some-tika-config.xml}} was breaking the
> commandline when running tika-app in batch mode.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
