[
https://issues.apache.org/jira/browse/OAK-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926595#comment-16926595
]
Vikas Saurabh commented on OAK-8532:
------------------------------------
Backported to 1.10 branch at [r1866744|https://svn.apache.org/r1866744] and to
1.8 branch at [r1866746|https://svn.apache.org/r1866746].
> Osgi based test to verify tika setup is working
> -----------------------------------------------
>
> Key: OAK-8532
> URL: https://issues.apache.org/jira/browse/OAK-8532
> Project: Jackrabbit Oak
> Issue Type: Test
> Components: search
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Major
> Fix For: 1.18.0, 1.10.5, 1.8.17
>
>
> Often it's found that we bump tika version while the setups using oak which
> are supposed to provide dependencies for tika do not bump dependencies
> version.
> That situation often leads to hidden errors that get detected very late as by
> definition we are expected to *not* fail on a text extraction (at best log a
> DEBUG log in \*BinaryTextExtractor.
> With current maven tests we don't hit that situation as maven takes care of
> pulling in dependencies transitively. We do miss out on having an OSGi based
> test which can kind of server 2 purposes:
> * notify us when we do bump tika version
> * serve as a reference for versions of dependencies that can work
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
