[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758241#action_12758241
]
Shalin Shekhar Mangar commented on SOLR-1449:
---------------------------------------------
bq. Note: I've marked this issue as Fix for 1.4 to try and give it some
visibility before the release since there seems to be some interest in getting
the release size smaller
I haven't seen the patch yet. But I do not understand why we need to copy the
jars in the released artifact. We can have some instructions or scripts (I
assume we don't want ant) to copy the jars to the correct places for running
solr-cell examples. Is there a problem with that?
> 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.
