[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761488#action_12761488
]
Shalin Shekhar Mangar commented on SOLR-1449:
---------------------------------------------
Hoss, Noble has been refactoring SolrConfig in SOLR-1198 with the end goal
being pluggable loading of SolrConfig. This makes SOLR-919 and SOLR-1293
easier. But it is also about how we want SolrPlugins to be loaded. Ideally
they'd keep configuration in SolrConfig but the actual loading will happen in
SolrCore or somewhere else outside.
A large part of work for SOLR-1198 has been done in 1.4. This patch also marked
for 1.4 goes against that example by modifying the resource loader. So we need
to ask now what is the function of SolrConfig? Do we want it to load/modify
SolrResourceLoader objects or just be a representation of configuration?
> 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
>
>
> 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.
