lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-5103) Plugin Improvements
Date Wed, 19 Aug 2015 13:33:46 GMT

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

Jan Høydahl commented on SOLR-5103:
-----------------------------------

bq. If someone wants to offer a plugin with dependency jars , please make a jar with all the
dependencies included.
Well that is for us to dictate, isn't it? Who says the plugin format must conform to the JAR
specs? Is it technically problematic to add all classes from multiple JARs from within a ZIP
to a classloader? If yes, the user-facing plugin format could still be a zip with multiple
jars in a lib folder, and our plugin installer code handles merging all jars together into
one jar {{plugin-xyz-merged.jar}} which is the one being registered with the classloader?

> Plugin Improvements
> -------------------
>
>                 Key: SOLR-5103
>                 URL: https://issues.apache.org/jira/browse/SOLR-5103
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>             Fix For: Trunk
>
>
> I think for 5.0, we should make it easier to add plugins by defining a plugin package,
ala a Hadoop Job jar, which is a self--contained archive of a plugin that can be easily installed
(even from the UI!) and configured programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message