nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sami Siren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NUTCH-609) Allow Plugins to be Loaded from Jar File(s)
Date Tue, 17 Feb 2009 14:37:03 GMT

    [ https://issues.apache.org/jira/browse/NUTCH-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674226#action_12674226
] 

Sami Siren commented on NUTCH-609:
----------------------------------

I think the direction in general is good, I know that we are the only ones feeling bad with
the current solution. We should perhaps put some more effort in thinking about a longer term
solution for the next generation Nutch.

> Allow Plugins to be Loaded from Jar File(s)
> -------------------------------------------
>
>                 Key: NUTCH-609
>                 URL: https://issues.apache.org/jira/browse/NUTCH-609
>             Project: Nutch
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>         Environment: All
>            Reporter: Dennis Kubes
>            Assignee: Dennis Kubes
>            Priority: Minor
>             Fix For: 1.0.0
>
>         Attachments: NUTCH-609-1-20080212.patch
>
>
> Currently plugins cannot be loaded from a jar file.  Plugins must be unzipped in one
or more directories specified by the plugin.folders config.  I have been thinking about an
extension to PluginRepository or PluginManifestParser (or both) that would allow plugins to
packaged into multiple independent jar files and placed on the classpath.  The system would
search the classpath for resources with the correct folder name and would load any plugins
in those jars.
> This functionality would be very useful in making the nutch core more flexible in terms
of packaging.  It would also help with web applications where we don't want to have a plugins
directory included in the webapp.
> Thoughts so far are unzipping those plugin jars into a common temp directory before loading.
 Another option is using something like commons vfs to interact with the jar files.  VFS essential
uses a disk based temporary cache for jar files, so it is pretty much the same solution. 
 What are everyone else's thoughts on this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message