I think for 2.0 we should consider splitting out parsers into their own projects for a streamlined dependency hierarchy then reassembling them with something like a tika-parsers-all artifact.
On June 17, 2014 at 5:08:38 PM, Nick Burch ([email protected]) wrote: > On Tue, 17 Jun 2014, Sergey Beryozkin wrote: > > The problem seems to be that Tika Parsers module contains many dependencies > > that may not be needed by a specific custom JAX-RS application. > > > > For example, we'd expect a given application dealing with PDF only, or a > > certain set of image formats only, or word docs only, etc. > > > > I'm not sure how many Tika-parsers dependencies are strongly required for > > any > > Tika application and which can be made optional. > > Just zap the Tika Parser dependency jars you don't want. All of the Tika > Parsers should by default silently fail if their dependencies are missing, > so after that going to /parsers/ you just won't see them there, and if you > try to parse that kind of document you'll get EmptyParser's result > instead. > > Nick >
