[
https://issues.apache.org/jira/browse/JCR-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712917#action_12712917
]
Jukka Zitting commented on JCR-1878:
------------------------------------
There is progress in Tika to address these concerns (for example the ICU4J
dependency was replaced by inlining just those classes that are really needed),
but I don't think we'll have a Tika 0.4 release out in time for Jackrabbit 1.6.
Thus I'm inclined to revert these (and JCR-1887) changes from the 1.x branch
and focus on Jackrabbit 2.0 for Tika integration.
> Use Apache Tika for text extraction
> -----------------------------------
>
> Key: JCR-1878
> URL: https://issues.apache.org/jira/browse/JCR-1878
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-text-extractors
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 1.6.0
>
>
> Once Apache Tika is released with a resolution to TIKA-175 (making Tika
> available to Java 1.4 projects), we should replace our direct parser library
> dependencies with Tika parsers. Ideally we'd just use the Tika
> AutoDetectParser that'll automatically detect the type of a binary and parse
> it accordingly, solving JCR-728.
> I guess we should keep some level of backwards compatibility with existing
> textFilterClasses="..." configurations, perhaps by keeping the existing
> TextExtractor classes as wrappers around respective Tika parsers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
