GitHub user nhojpatrick opened a pull request:
https://github.com/apache/tika/pull/76
TIKA-1868 tika-server split into clean and standalone jar
Understand based upon mailing email and jira defect this might be rejected.
But this the change I was intending to do, my original email was to
understand if tika-server meant to be a shaded jar, which it appears to was
intended to be.
But if you need to use classes that only live within tika-server it does
make it harder to write custom code. If the guts of tika-server where put into
another module maybe tika-server-internals then those that really need to used
classes that just live in tika-server can use tika-server-internals and
tika-server can be a simply shaded jar. Just a thought.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nhojpatrick/tika bugfix/TIKA-1868
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tika/pull/76.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #76
----
commit 9b106210fa8be284b47ab5b904dcf83b0f175308
Author: John Patrick <nhoj.patr...@gmail.com>
Date: 2016-02-24T12:33:56Z
TIKA-1868 tika-server split into clean and standalone jar
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
