[
https://issues.apache.org/jira/browse/SOLR-17883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024126#comment-18024126
]
ASF subversion and git services commented on SOLR-17883:
--------------------------------------------------------
Commit 871811214ef9f54e2071f14c386603f4eb5e9a1f in solr's branch
refs/heads/branch_9_9 from Jason Gerlowski
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=871811214ef ]
SOLR-17883: Add <install>/lib to tool classpath (#3566)
Prior to this commit, the classpath for tools like "bin/solr zk"
consisted only of directories like `server/lib/ext` that already serve a
particular purpose (e.g. webapp libs, Jetty libs, etc). There was no
great place to put plugin jars needed by "bin/solr".
This commit addresses this by adding `<install>/lib` to the tool
classpath. This directory is already on Solr's classpath, so jars put
here are accessible by SolrCLI tools, as well as the Solr server proper.
> "bin/solr" tools should have more expansive classpath
> -----------------------------------------------------
>
> Key: SOLR-17883
> URL: https://issues.apache.org/jira/browse/SOLR-17883
> Project: Solr
> Issue Type: Improvement
> Components: SolrCLI
> Affects Versions: 9.9
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Labels: pull-request-available
> Fix For: main (10.0), 9.10
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The ref-guide singles out {{<solr_install>/lib}} as being a particularly good
> place to put plugin jars during Dockerfile packaging:
> bq. The .jar files placed here are available to all Solr cores running on the
> node, and to node level plugins referenced in solr.xml — so basically
> everything. Contrary to <solr_home>/lib/, this directory is always located in
> the install dir, so it can be used e.g. for custom Dockerfile to place custom
> plugin jars.
> But this comes with a bit of a hidden catch: the directory is on the
> classpath of Solr server, but it's *not* on the classpath for "bin/solr"
> tools more generally. There may be other cases, but I've seen this cause
> issues with "bin/solr zk" in particular, where users may want to use their
> own ZkAclProvider or ZkCredProvider implementations with "bin/solr zk".
> We should add {{<solr_install>/lib}} to the tool classpath, or update the
> ref-guide with other guidance on where jars can be placed to be loadable by
> the bin/solr tools.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
