[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758462#action_12758462
]
Hoss Man commented on SOLR-1449:
--------------------------------
I feel like these comments aren't really on topic ... this type of feature has
been discussed numerous times on the list as a desirable way for users to
specify where a core should look to load plugins without needing to copy jars
to a specific hardcoded directory -- particularly when people want to use the
same plugins in multiple cores (that have unique instanceDirs)
Independent of any question of what our releases look like, and what kinds of
examples we want to include, these is still a feature that users have been
requesting.
My point about our examples was merely that an *additional* use case that would
be improved by this feature is that we would be able to have a single copy of
any jar in the release, no matter how many examples wanted to refer to it
(which would also make it easier to add examples that would work "as is"
without debating the potential increase n the size of the release, or wether we
should ask the user to copy the jars, etc...
bq. It's just that having a regex based class loading from externally located
jars, although cool, seems an overly fancy way to solve this particular problem.
As i already said: that wasn't a particular goal, just a nice side effect --
but FWIW: the regex based loading was actually the easiest way i found to
identify multiple jars -- i was looking for an easy way to do shell style
fileglobbing in java and nothing jumped out at me, java.util.regex on the other
hand is a stock and easy to use.
> 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.
