[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759216#action_12759216
]
Hoss Man commented on SOLR-1449:
--------------------------------
bq. That is taken care of by the sharedLib attribute in solr.xml
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)
bq. I'm not a classloading expert... but couldn't this cause things to work
differently by changing the order of the <lib> statements?
Excellent point ... yes you have to declare things in a dependency order. This
didn't seem like a big deal to me when i first wrote it, but i can see how that
could prove very tedious, it could make it impossible to use some sets of jars
without having them in a specific set of directories.
The other option was to maintain a list of all the jars in parallel with the
"current" classloader, and replace the classloader anytime new jars were added
-- this seemed like a bigger evil to me originally because it made the behavior
*really* unpredictable if someone tried to use the class loader in the middle
of adding more jars (because there would be classes that had been loaded by a
classloader that was no longer in use) but frankly: i don't see how the
behavior would really be any weirder then what would currently happen, and it
would certainly be nice to make it less dependent on the order things were
declared.
I'll try to get another patch up today.
> 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.
