It appears that Tika comes in two flavors, library JARs and an all-in-on “app” JAR. Which JAR(s) are you using? It should NOT be tika-app because that probably includes a bunch of third-party stuff that is needed to run it as a stand-alone application (such as slf4j). What you probably want is tika-core and/or tika-parsers.
From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Joakim Erdfelt
Sent: Monday, August 18, 2014 1:26 PM
To: JETTY user mailing list
Subject: Re: [jetty-users] class version problem - use modules?
That seems to be a slf4j version mismatch.
Be sure that you are using slf4j 1.6.4+
And that you are using the same versions of slf4j on the server and your webapp's WEB-INF/lib.
Expert advice, services and support from from the Jetty & CometD experts
On Fri, Aug 15, 2014 at 12:18 PM, Rob Nikander <rob.nikander@xxxxxxxxx> wrote:
I've been blissfully ignorant and simply putting jars into lib/ext or the app's WEB-INF/lib, but today I hit a problem trying to use Apache Tika. If I put the tika jar in lib/ext, Jetty fails to start , and I'm wondering if it's because the Tika jar has an older version of an slf4j class.
Is this something I can get around with modules? Maybe I can add the tika jar but keeps its copy of slf4j classes private to itself? I remember jboss modules doing something like this, but I don't see anything on the doc page 
jetty-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit