[jira] [Commented] (JCR-2885) Move tika-parsers dependency to deployment packages

["Julian Reschke (JIRA)" <ji...@apache.org>]

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

Julian Reschke commented on JCR-2885:
-------------------------------------

trunk: [r1076635|http://svn.apache.org/r1076635] [r1072006|http://svn.apache.org/r1072006] [r1071611|http://svn.apache.org/r1071611]


> Move tika-parsers dependency to deployment packages
> ---------------------------------------------------
>
>                 Key: JCR-2885
>                 URL: https://issues.apache.org/jira/browse/JCR-2885
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core, jackrabbit-jca, jackrabbit-webapp
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 2.3
>
>
> As discussed on the mailing list, it would be better if the tika-parsers dependency (and all the parser libraries it pulls in transitively) was included in our deployment packages but not directly in jackrabbit-core. This would make it easier for people to set up custom lightweight deployments with no or only partial full text extraction functionality.
> To do this we'll first need to wait for Tika 0.9, as we currently have a custom PDFParser class in jackrabbit-core as a workaround to a problem in Tika 0.8.
> At the same time we should do a more thorough review of the transitive parser dependencies we include. At least the rome and bouncycastle libraries were flagged as potentially unnecessary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)