[
https://issues.apache.org/jira/browse/NUTCH-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470990#comment-17470990
]
ASF GitHub Bot commented on NUTCH-2429:
---------------------------------------
lewismc merged pull request #720:
URL: https://github.com/apache/nutch/pull/720
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@nutch.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix Plugin System to allow protocol plugins to bundle their URLStreamHandlers
> -----------------------------------------------------------------------------
>
> Key: NUTCH-2429
> URL: https://issues.apache.org/jira/browse/NUTCH-2429
> Project: Nutch
> Issue Type: Improvement
> Components: commoncrawl
> Affects Versions: 1.14
> Environment: Tested on both Nutch 1.13 and 1.14 in Ubuntu Linux with
> OpenJDK 1.8.
> Reporter: Hiran Chaudhuri
> Priority: Major
> Fix For: 1.19
>
>
> While trying to use the protocol-smb plugin (which is not part of the Nutch
> distribution) I realized there are four steps to successfully make use of a
> protocol plugin:
> 1 - put the artifact into the plugins directory
> 2 - modify Nutch configuration files to allow smb:// urls plus include the
> plugin to the loaded list
> 3 - extract jcifs.jar and place it on the system classpath
> 4 - run nutch with the correct system property
> While steps 1 and 2 seem obvious, 3 and 4 require knowledge of plugin
> internals which does not feel right for nutch and plugin users. Even more,
> the jcifs.jar would exist twice on the classpath and could even cause further
> problems during runtime.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
