jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2885) Move tika-parsers dependency to deployment packages
Date Thu, 10 Mar 2011 14:33:59 GMT

     [ https://issues.apache.org/jira/browse/JCR-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting resolved JCR-2885.

    Resolution: Fixed

Resolving as fixed based on the above changes.

> 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.0
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message