[
https://issues.apache.org/jira/browse/NUTCH-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567405#action_12567405
]
Dennis Kubes commented on NUTCH-609:
------------------------------------
Sorry, I should have been more clear. I know that it is possible to load the
resources directly from the jar files, I just don't how much work that is going
to take. I agree that avoiding the unzipping of jar files into temp
directories and having to manage those directories for deletion is the
preferred solution.
Another thing I was thinking of and would like to get thoughts on is a
convention versus configuration solution. Instead of browsing jar files for
named resources, and then having to deal with the contention issues between
directories and resources in jars being named the same, what if we were to have
plugin jar files named a given way, something like name-plugin.jar. For
example the prefix urlfilter plugin would be named urlfilter-prefix-plugin.jar.
There would be a single plugin per jar and each jar would be the root
directory for its plugin. Then to find plugin jars we are just scanning the
classpath for certain named jars. The downside to this is we could end up with
a lot of jars, but currently we are ending up with a lot of folders so I don't
know if that is a big difference. Thoughts?
> 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
> Fix For: 1.0.0
>
>
> 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.
