[jira] [Commented] (TIKA-1368) Improve the modularity of tika-parsers

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

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

Sergey Beryozkin commented on TIKA-1368:
----------------------------------------

The documentation needs to be in place before this issue can be addressed

> Improve the modularity of tika-parsers
> --------------------------------------
>
>                 Key: TIKA-1368
>                 URL: https://issues.apache.org/jira/browse/TIKA-1368
>             Project: Tika
>          Issue Type: Improvement
>          Components: packaging, parser
>    Affects Versions: 1.7
>            Reporter: Sergey Beryozkin
>
> tika-parsers module has many strong transitive dependencies. This presents a challenge to Maven tika-parsers users wishing to use only one or very few Parser(s).
> The fact the new Parsers are regularly added makes the exclusion process very brittle. For example, an OSGI application switching from Tika 1.6 to Tika 1.7 and having an exclusion list in place may 'leak' a new parser lib into its runtime. 
> https://issues.apache.org/jira/browse/TIKA-1367
> can help on its own but a more complete solution would ideally be in place.
> Proposal:
> 1. Make tika-parsers transitive dependencies optional
> 2. Introduce tika-parsers-optional pom that will depend on tika-parsers but exclude 3rd-party dependencies
> Both 1 and 2 will depend on the resolution of TIKA-1367. IMHO 1 is cleaner, users will be recommended to check the documentation and add the required dependencies. 2 also works.



--
This message was sent by Atlassian JIRA
(v6.2#6252)