[
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703050#comment-14703050
]
Shawn Heisey commented on SOLR-5103:
------------------------------------
bq. If someone wants to offer a plugin with dependency jars , please make a jar
with all the dependencies included. Once you make that assumption everything
else becomes simpler.
I worry about this idea a little bit. Maybe I don't need to be worried. What
happens if a plugin project uses one of the same dependent jars as Solr, but
packages a wildly different version than the version we package? Are there any
situations where that might cause a larger problem than using a little more
memory?
> 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: [email protected]
For additional commands, e-mail: [email protected]
