Cheers for everyone's responses and feedback. Believe I've resolved the issue in the correct Tika way once merges are accepted and 1.13 is released.
Refactor replacing TIKA-1668 https://issues.apache.org/jira/browse/TIKA-1870 https://github.com/apache/tika/pull/77 John On 24 February 2016 at 13:30, John Patrick <[email protected]> wrote: > Cheers for replies, I now understand how tika developers intended > tika-server should be used but for the custom code we have written we need > to use a few classes that only live in tika-server. > > For Jackson I've done that as a seperate pull request. > > tika-server restructure > https://issues.apache.org/jira/browse/TIKA-1868 > https://github.com/apache/tika/pull/75 > > Jackson upgrade; > https://issues.apache.org/jira/browse/TIKA-1869 > https://github.com/apache/tika/pull/76 > > Cheers, > John > > > > On 23 February 2016 at 19:41, Nick Burch <[email protected]> wrote: > >> On Tue, 23 Feb 2016, John Patrick wrote: >> >>> I'm working with an existing code base that is using Jackson 2.6.3. Now >>> adding tika but because the tika-server jar containers Jackson 2.4.0 >>> having >>> lots of compile issues. >>> >>> 1) Was it intentional to have a bloated/fat tika-server jar containing >>> all >>> dependencies? >>> >> >> Yes. Both the Tika App and Tika Server jars are intended to be single >> runnable downloads, with everything in you need to use Tika. (Ideally we'd >> also have the Tika Server as a war, but that's ongoing) >> >> 2) Can tika be upgraded to use Jackson 2.6.3 or newer? >>> >> >> In general, when there are new releases of libraries that Tika depends >> on, with useful bug fixes, then we upgrade. Does require someone to notice >> + open a bug + contribute any fixes required to keep things working. Hint >> hint... :) >> >> 3) Can tika-server but corrected so it's not bloated with dependencies, or >>> create tika-server with just org.apache.tika.server and tika-server-all >>> which is the bloating version with dependencies? >>> >> >> I'm not sure what the point of a Tika Server with no parsers or detectors >> in would be, which is what you'd get if you excluded all the dependencies. >> Could you clarify your use-case? >> >> Nick >> > >
