[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759409#action_12759409
]
Noble Paul commented on SOLR-1449:
----------------------------------
I have a few questions in mind.
* Is this an issue which users have reported? in my experience with Solr
mailing list, I am yet to see a request where users wish to add arbitrary
directories to classpath
* How important is this feature to be in 1.4?
I am not aware of any project which allows this level of configurability for
classpath. Most of the users never have to write custom components for Solr. In
our organization, I have encountered very few cases where they needed to add
custom jars to classpath. Even in cases where they did , they were some trivial
jars.
I am -1 on adding this to 1.4.
> 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, 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.
