tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TIKA-173) Creating of a binary release that does not bundle all JARS in one big one
Date Sat, 15 Nov 2008 22:53:46 GMT

    [ https://issues.apache.org/jira/browse/TIKA-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647907#action_12647907

Jukka Zitting commented on TIKA-173:

Also, as for the Maven goal that creates a directory with all the dependency jars, run "mvn
dependency:copy-dependencies" and look at "target/dependency".

> Creating of a binary release that does not bundle all JARS in one big one
> -------------------------------------------------------------------------
>                 Key: TIKA-173
>                 URL: https://issues.apache.org/jira/browse/TIKA-173
>             Project: Tika
>          Issue Type: Wish
>    Affects Versions: 0.2-incubating
>            Reporter: Uwe Schindler
> The maven code for building the project works good. For me it is a little bit annoying
that you are not able (as end user who will just download a binary release for inclusion into
his project) to include the JAR and all dependent JARs into your project. The standalone JAR
is good for starting TIKA as GUI or for a simple command line, but when including it into
other projects, where some of the libraries used by TIKA are also used, you have duplicate
class entries in your classpath and depending on the position of the standalone.jar you may
overwrite your local classes by old versions.
> It would be good to have a maven build task/step, that creates a lib directory for the
binary release containing TIKA's JAR file and all dependant libs as separate files. Then a
user is possible to only add the missing libs to his own project and e.g. replace by newer
versions of PDFBox, POI, XALAN, XERCES and do not pollute his classpath.
> By the way: TIKA is a Java 1.5 Project, the use of xml-apis.jar is not good. JAXP is
already included in Java, so i would remove this from the dependencies.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message