[ https://issues.apache.org/jira/browse/TIKA-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison resolved TIKA-2653. ------------------------------- Resolution: Fixed Fix Version/s: 2.0.0 1.19 [~lfcnassif], we can always fix later. Let me know what you think! Thank you! > 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 > Assignee: Tim Allison > Priority: Major > Fix For: 1.19, 2.0.0 > > > 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)