[
https://issues.apache.org/jira/browse/TIKA-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382272#comment-16382272
]
Nick Burch commented on TIKA-2595:
----------------------------------
Binaries of all Apache Tika jars are available from Maven central
The Tika Core and Tika Parsers jars aren't all that much use on their own, you
generally need to supply the parser dependencies in order to be able to process
much with them. Since you don't normally want to do that by hand, and will want
to use a dependency management tool to do that for you, we feel most users of
the libraries will use Maven / Ivy / Gradle etc to pull down Tika + desired
dependencies
Since the Tika App and Tika Server are standalone and can be used by non-Java
developers, we dual publish those to both maven central and to the website
If you want to add all your dependencies by hand, you can grab the official
jars from maven central
> If source build creates 6 jars, why aren't all 6 binaries available for
> download?
> ---------------------------------------------------------------------------------
>
> Key: TIKA-2595
> URL: https://issues.apache.org/jira/browse/TIKA-2595
> Project: Tika
> Issue Type: Bug
> Components: packaging
> Affects Versions: 1.17
> Reporter: Andrew Pavlin
> Priority: Major
>
> My company would like to use Tika, but some of the libraries Tika includes
> may not be compatible with our licensing. We notice that the source build
> creates 6 different binary JAR files, but only 3 of them are available for
> download (the 2 largest ones with the most extra baggage we don't need, and a
> test tool we don't need either). For various legal reasons, we can't create
> our own JAR files from source; we have to use the officially built ones from
> Apache. Could the smaller binary JAR files (tika-core and tika-parsers) be
> made available for download?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
