You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2019/08/08 02:09:00 UTC
[jira] [Commented] (OAK-8532) Osgi based test to verify tika setup
is working
[ https://issues.apache.org/jira/browse/OAK-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902591#comment-16902591 ]
Vikas Saurabh commented on OAK-8532:
------------------------------------
Additional resources broke build due to missing licenses (OAK-8533). Fixed that at [r1864674|https://svn.apache.org/r1864674].
> 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
>
>
> 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
> * server as a reference for versions of dependecies that can work
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)