You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (Jira)" <ji...@apache.org> on 2021/09/22 15:56:00 UTC

[jira] [Commented] (NUTCH-2895) Allow to add plugin dependency jars by wildcard

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

Lewis John McGibbney commented on NUTCH-2895:
---------------------------------------------

I agree with your motivation here Seb. I need to study this some...

> Allow to add plugin dependency jars by wildcard
> -----------------------------------------------
>
>                 Key: NUTCH-2895
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2895
>             Project: Nutch
>          Issue Type: Improvement
>          Components: plugin, runtime
>    Affects Versions: 1.18
>            Reporter: Sebastian Nagel
>            Priority: Major
>             Fix For: 1.19
>
>
> The plugin descriptors (plugin.xml) require to list all dependent jar files one by one as "library". This makes upgrading plugins which include a longer list of dependencies (parse-tika, any23, protocol-okhttp, Selenium-based protocols) a non-trivial task. Maybe we could add a "wildcard" rule that allows to add all (remaining) jars in the plugin folder to the classpath.
> Sure this would make the Nutch plugin system differ from the [original Eclipse plugin architecture|http://www.eclipse.org/articles/Article-Plug-in-architecture/plugin_architecture.html]. When looking into recent Eclipse plugins: dependencies are in the lib/ folder and listed in the file "MANIFEST.MF".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)