[
https://issues.apache.org/jira/browse/TIKA-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032177#comment-18032177
]
Tim Allison commented on TIKA-4512:
-----------------------------------
The draft PR now works through {{{}tika-core-tests{}}}. Some things of concern:
* The json everywhere thing mentioned above
* There are now two config files – one tika-config.xml for all the parsers,
detectors and other legacy components and one plugins.json to deal with all the
plugins/pipes components. This feels ugly...perhaps we move to all json by Tika
5.x :D
* I've had to do some hackery to be able to test tika-pipes-core with the
file-system-fetcher. I think it is really important to use actual plugin
artifacts in tests rather than relying on the "development mode" of pf4j.
* I'm not sure if we should rely on the parent project's databind or if we
should put that in every plugin (which I don't like).
> Experiment with pf4j for tika-pipes
> -----------------------------------
>
> Key: TIKA-4512
> URL: https://issues.apache.org/jira/browse/TIKA-4512
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Priority: Major
>
> This is proof of concept work based on [~ndipiazza] 's TIKA-4272-docker
> branch.
> I really like a lot of that work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
