[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762073#action_12762073
]
Hoss Man commented on SOLR-1449:
--------------------------------
bq. 1. Should the change in clustering/example/conf/schema.xml be part of this
patch?
...probably not, i totally forgot i had to make that fix to get the example
working. i'll try to commit that seperately tonight.
bq. 5. Did you consider just extending URLClassLoader and opening up addUrl
rather than replacing the loader? Almost seems nicer - no biggie though.
I went down the road, but i ran into a problem -- i don't remember the
specifics, i was probably doing something stupid, but in trying to figure it
out i noticed the caveat about using addURL...
{noformat}
"The classes that are loaded are by default granted permission only
to access the URLs specified when the URLClassLoader was created.
{noformat}
...and figured it was safer just to go this way and document that you should
only modify the classloader prior to using the ResourceLoader.
6. What about solr.xml's sharedlib setting? Should it support the same syntax
options as the
solrconfig lib setting ?
we can always add the syntax to solr.xml as well -- but that gets more
challanging because of the persistence options, so i punted on it for now.
> 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
> Assignee: Hoss Man
> Fix For: 1.4
>
> Attachments: SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch,
> SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch,
> 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.
