[jira] [Commented] (TIKA-3955) separate dependencies from tika-app-2.6.0-noasm-nojson

2023-01-12 Thread Tim Allison (Jira)


[ 
https://issues.apache.org/jira/browse/TIKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676246#comment-17676246
 ] 

Tim Allison commented on TIKA-3955:
---

See the "tika-parsers module" section: 
https://cwiki.apache.org/confluence/display/TIKA/Migrating+to+Tika+2.0.0

> separate dependencies from tika-app-2.6.0-noasm-nojson 
> ---
>
> Key: TIKA-3955
> URL: https://issues.apache.org/jira/browse/TIKA-3955
> Project: Tika
>  Issue Type: Wish
>Reporter: Dhoka Pramod
>Priority: Major
>
> Hi Team,
> We are using tika-app-2.6.0-noasm-nojson.jar (uber jar) and it is bundled 
> with all the required third-party jars as mentioned below
> activation-1.1.1.jar
> bcmail-jdk18on-1.72.jar
> bcpkix-jdk18on-1.72.jar
> bcprov-jdk18on-1.72.jar
> byte-buddy-1.12.7.jar
> commons-cli-1.4.jar
> commons-codec-1.15.jar
> commons-collections4-4.1.jar
> commons-compress-1.21.jar
> commons-exec-1.0.jar
> commons-io-2.11.0.jar
> commons-lang3-3.8.1.jar
> commons-logging-1.1.1.jar
> gson-2.9.0.jar
> jackson-core-2.14.0.jar
> jackson-databind-2.14.0.jar
> jaxb-impl-2.1.13.jar
> jaxen-1.1.6.jar
> juniversalchardet-1.0.3.jar
> log4j-api-2.19.0.jar
> log4j-core-2.19.0.jar
> slf4j-api-1.7.36.jar
> xercesImpl.jar
> xmlbeans-3.1.0.jar
> Our application also adds the above jars as it requires. This is leading to 
> duplicate classes on the classpath. Could you provide the tika-app jar 
> (skinny jar) and a list of required dependencies so that we will add them to 
> our application classpath to avoid duplicates.
> Thank you.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (TIKA-3955) separate dependencies from tika-app-2.6.0-noasm-nojson

2023-01-12 Thread Nick Burch (Jira)


[ 
https://issues.apache.org/jira/browse/TIKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675914#comment-17675914
 ] 

Nick Burch commented on TIKA-3955:
--

The Tika App is intended as a "batteries included" standalone app.

If you are adding Tika to a Java app, you should add the Java library. Include 
`tika-core` and as many of the `tika-parser-*` parsers as your application 
needs. Doing that via Maven or Gradle will allow you to manage any dependency 
clashes

> separate dependencies from tika-app-2.6.0-noasm-nojson 
> ---
>
> Key: TIKA-3955
> URL: https://issues.apache.org/jira/browse/TIKA-3955
> Project: Tika
>  Issue Type: Wish
>Reporter: Dhoka Pramod
>Priority: Major
>
> Hi Team,
> We are using tika-app-2.6.0-noasm-nojson.jar (uber jar) and it is bundled 
> with all the required third-party jars as mentioned below
> activation-1.1.1.jar
> bcmail-jdk18on-1.72.jar
> bcpkix-jdk18on-1.72.jar
> bcprov-jdk18on-1.72.jar
> byte-buddy-1.12.7.jar
> commons-cli-1.4.jar
> commons-codec-1.15.jar
> commons-collections4-4.1.jar
> commons-compress-1.21.jar
> commons-exec-1.0.jar
> commons-io-2.11.0.jar
> commons-lang3-3.8.1.jar
> commons-logging-1.1.1.jar
> gson-2.9.0.jar
> jackson-core-2.14.0.jar
> jackson-databind-2.14.0.jar
> jaxb-impl-2.1.13.jar
> jaxen-1.1.6.jar
> juniversalchardet-1.0.3.jar
> log4j-api-2.19.0.jar
> log4j-core-2.19.0.jar
> slf4j-api-1.7.36.jar
> xercesImpl.jar
> xmlbeans-3.1.0.jar
> Our application also adds the above jars as it requires. This is leading to 
> duplicate classes on the classpath. Could you provide the tika-app jar 
> (skinny jar) and a list of required dependencies so that we will add them to 
> our application classpath to avoid duplicates.
> Thank you.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)