[
https://issues.apache.org/jira/browse/TIKA-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440740#comment-17440740
]
Hudson commented on TIKA-3589:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #354 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/354/])
TIKA-3589 -- fix default logging in tika-app in batch mode and --config= in
tika-app in batch mode (tallison:
[https://github.com/apache/tika/commit/67f03bc04ddf5d9c146822d4723b1c76a634a773])
* (edit) CHANGES.txt
* (edit)
tika-app/src/test/java/org/apache/tika/cli/TikaCLIBatchIntegrationTest.java
* (edit) tika-app/src/test/resources/test-data/tika-config1.xml
* (edit) tika-app/src/main/java/org/apache/tika/cli/BatchCommandLineBuilder.java
> 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)
