[
https://issues.apache.org/jira/browse/TIKA-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392300#comment-17392300
]
Tim Allison commented on TIKA-3510:
-----------------------------------
The goal was to make it possible for users to drop the sqlite3 jar and/or the
scientific-module jar on their path with the tika-parsers-standard-package or
tika-app/tika-server and have everything just work.
If there's a better way to accomplish this, let me know.
One thing we could do is what we do in tika-parsers-standard and have a module
_and_ package project for the scientific-module and the sqlite3 module. We'd
include the dependencies in the jar in *_package but not in *_module.
Would this be of any use? Or can you recommend a better fix?
> tika-parser-scientific-module seems to embbed many dependencies
> ---------------------------------------------------------------
>
> Key: TIKA-3510
> URL: https://issues.apache.org/jira/browse/TIKA-3510
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 2.0.0
> Reporter: Thomas Mortagne
> Priority: Major
>
> tika-parser-scientific-module 2.0.0 contains many files from other artifacts:
> * joda-time
> * slf4j
> * commons-io
> * ...
> Is that really expected ?
> tika-parser-sqlite3-module seems to be affected too
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
