[
https://issues.apache.org/jira/browse/NUTCH-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567407#action_12567407
]
Chris A. Mattmann commented on NUTCH-609:
-----------------------------------------
bq. 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?
+1 for this strategy, even if it manes having more jar files to manage.
Adopting this strategy would suggest to a more component-based build management
system, e.g., a Maven-type. I've been a proponent of using Maven in Nutch for a
while, and I think to move the plugins to a .jar file format would ease their
adoption as say, remotely downloable Maven style plugins, that then Nutch would
rely upon. Then, we could get out of the business of having to CM jar files,
which I've never been a fan of.
> 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.
