[
https://issues.apache.org/jira/browse/TIKA-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123595#comment-18123595
]
Hudson commented on TIKA-4953:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1695 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1695/])
TIKA-4953: add PipesParser.start() and PipesForkParser.start() (#3299) (github:
[https://github.com/apache/tika/commit/4abbb31ee11b59de4dc8f4c2052a3eabaada25b9])
* (edit) docs/modules/ROOT/pages/using-tika/java-api/pipes.adoc
* (edit)
tika-pipes/tika-pipes-fork-parser/src/main/java/org/apache/tika/pipes/fork/PipesForkParser.java
* (add)
tika-pipes/tika-pipes-integration-tests/src/test/java/org/apache/tika/pipes/core/PipesStartupTest.java
* (edit) CHANGES.txt
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/PipesParser.java
* (edit)
tika-pipes/tika-pipes-fork-parser/src/test/java/org/apache/tika/pipes/fork/PipesForkParserTest.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/PipesClient.java
> Add start() to PIpesForkParser
> ------------------------------
>
> Key: TIKA-4953
> URL: https://issues.apache.org/jira/browse/TIKA-4953
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
>
> During the migration to 4.1.0 on StormCrawler, [~dpol1] noted that it is a
> pain to find configuration files in PipesServer only on the first parse.
> We should add a start() or similar so that config problems can be found
> sooner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
