[
https://issues.apache.org/jira/browse/TIKA-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491227#comment-16491227
]
Tim Allison commented on TIKA-2653:
-----------------------------------
I've pushed a very rough draft to the TIKA-2653 branch. I need to flesh out a
bit more about how to inject a tika-config and some other stuff. However,
generally, does this look ok? The ForkParser is a thing of elegance, and I
don't want to mar it.
> Allow users to specify a directory of jars for classloading in ForkParser
> -------------------------------------------------------------------------
>
> Key: TIKA-2653
> URL: https://issues.apache.org/jira/browse/TIKA-2653
> Project: Tika
> Issue Type: New Feature
> Reporter: Tim Allison
> Priority: Major
>
> The ForkParser now builds the parser in the parent process and serializes it
> to the child process. It would be neat to make it easier for users of the
> ForkParser to depend solely on tika-core and put all of our dependency
> nastiness in a separate directory that will be used by the the fork server
> (child process) to build the underlying parser.
> This would allow, e.g. Solr, to point to a directory with the tika-app.jar
> and remove all of our dependencies (except tika-core) from their
> dependencies.
> I propose that we allow users to initialize ForkParser with a Path that
> contains all the jars necessary to build the Parser, and, optionally, a
> ParserFactory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
