[
https://issues.apache.org/jira/browse/JCR-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737453#comment-17737453
]
Chris Poulsen commented on JCR-4832:
------------------------------------
The issue is very much still present, AFAIK! Our logs are full of crap (a bunch
of errors/stack traces) when we start up the new versions.
The configuration of the bundled TIKA does not match the provided dependencies,
so there is no surprise that there are errors about missing classes.
I never got around to check, but I'm also pretty sure that the indexes built
with the newer versions take up less space on disk (probably an indication that
the indexing is not including the same stuff as it did with previous versions).
We do not seem to rely on the features from TIKA, so it seems that the
functionality we use is unaffected. So far we have just crossed our fingers
that it did not start to break stuff at some point and kept on going with our
daily work.
> commons-compress jar seems to be missing in JCA archive
> -------------------------------------------------------
>
> Key: JCR-4832
> URL: https://issues.apache.org/jira/browse/JCR-4832
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jca
> Affects Versions: 2.20.6
> Reporter: Chris Poulsen
> Priority: Major
> Attachments: tika-commons-compress.txt
>
>
> I'm trying to upgrade to Jackrabbit v2.20.6 as part of a larger dependency
> update.
> We use the JCA archive because we need XA transactions.
> During deployment of the 2.20.6 archive I see stacktraces with:
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.compress.compressors.CompressorException {code}
> (More complete log attached)
> As far as I can tell, you include:
> {code:java}
> org.apache.tika:tika-parser-zip-commons:2.4.0{code}
> Which in turn has a dependency on:
> {code:java}
> org.apache.commons:commons-compress:1.21 {code}
> And the latter is not present in the JCA archive.
> I do not think that we are relying much on the Tika stuff, but I am a bit
> worried that something is not working correctly based on all these stack
> traces.
> I guess the missing dependency is a bug.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
