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
