[
https://issues.apache.org/jira/browse/TIKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044407#comment-18044407
]
Tim Allison edited comment on TIKA-4545 at 12/11/25 11:46 AM:
--------------------------------------------------------------
Ugh. Sorry. I opened https://issues.apache.org/jira/browse/TIKA-4564 to fix
this generally and to switch to actual json manipulation and not the hacky
string replace we were doing.
Does this mean our dockerized tests aren't running in Github ci?
was (Author: [email protected]):
Ugh. Sorry. I opened https://issues.apache.org/jira/browse/TIKA-4564 to fix
this generally and to switch to actual json manipulation and not the hacky
string manipulation we were doing.
> Fully integrate new json based deserializer in 4.x
> --------------------------------------------------
>
> Key: TIKA-4545
> URL: https://issues.apache.org/jira/browse/TIKA-4545
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Fix For: 4.0.0
>
>
> Follow on for TIKA-4544.
> Steps:
> * Add annotations to components (parsers, etc.) and unit tests to confirm
> they work (finished this today)
> * Modify components (parsers etc), at least a few of them so that they are
> actually configurable. We don't have to modify all, just the most important
> ones PDFParser, tesseract, MSOffice, and others???
> * Move to tika-config.json in tika-pipes client/server, tika-async-cli,
> tika-app and tika-server one by one
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
