[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759230#action_12759230
]
Shalin Shekhar Mangar commented on SOLR-1449:
---------------------------------------------
bq. sharedLib only helps if you want the same plugins in every core (not just
to reuse the same plugins in multiple cores. There's also no way to reload a
plugin from the sharedLib (whereas the normal lib for a core does get reloaded
when the core is reloaded)
OK, that's true.
bq. As i already said: that wasn't a particular goal, just a nice side effect -
but FWIW: the regex based loading was actually the easiest way i found to
identify multiple jar
I understand you want to make a core's lib directory configurable. That is
fine. It is the regex based loading that makes me nervous. Why not load all
jars in a specified directory?
> solrconfig.xml syntax to add classpath elements from outside of instanceDir
> ---------------------------------------------------------------------------
>
> Key: SOLR-1449
> URL: https://issues.apache.org/jira/browse/SOLR-1449
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1449.patch
>
>
> the idea has been discussed numerous times that it would be nice if there was
> a way to configure a core to load plugins from specific jars (or "classes"
> style directories) by path w/o needing to copy them to the "./lib" dir in
> the instanceDir.
> The current workaround is "symlinks" but that doesn't really help the
> situation of the Solr Release artifacts, where we wind up making numerous
> copies of jars to support multiple example directories (you can't have
> reliable symlinks in zip files)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
