You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2020/08/21 17:11:00 UTC

[jira] [Commented] (TIKA-3179) Tika 2.0.0 -- Clean up parser module hierarchy

    [ https://issues.apache.org/jira/browse/TIKA-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182028#comment-17182028 ] 

Tim Allison commented on TIKA-3179:
-----------------------------------

We should also clean up the module names under {{tika-advanced-parser-modules}}.

> Tika 2.0.0 -- Clean up parser module hierarchy
> ----------------------------------------------
>
>                 Key: TIKA-3179
>                 URL: https://issues.apache.org/jira/browse/TIKA-3179
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Critical
>              Labels: 2.0.0
>
> As a first step, I put most of the parsers under tika-parser-modules.  I moved a few under tika-advanced-parser-modules.
> tika-parsers currently includes most parsers under tika-parser-modules, but it skips scientific and db because of dependencies.
> Two options that come to mind.
> 1) Add a tika-parsers-extended that includes tika-parsers and the missing parsers.  What I don't like about this and the current setup is that "tika-parsers" is outside of tika-parser-modules...
> 2) Delete "tika-parsers"; create two "module" level modules: "tika-parsers-module" and "tika-parsers-extended-module", move the two big dependency modules to "tika-parsers-extended-module" and then have tika-app and tika-server use tika-parsers-module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)