gerlowskija opened a new pull request, #3566:
URL: https://github.com/apache/solr/pull/3566

   https://issues.apache.org/jira/browse/SOLR-17883
   
   # Description
   
   The classpath for tools like "bin/solr zk" consists only of directories like 
`server/lib/ext` that already serve a particular purpose (e.g. webapp libs, 
Jetty libs, etc).  There's no great place to put plugin jars needed by 
"bin/solr".
   
   # Solution
   
   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.
   
   # Tests
   
   Manual testing
   
   # Checklist
   
   Please review the following and check all that apply:
   
   - [x] I have reviewed the guidelines for [How to 
Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my 
code conforms to the standards described there to the best of my ability.
   - [x] I have created a Jira issue and added the issue ID to my pull request 
title.
   - [x] I have given Solr maintainers 
[access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
 to contribute to my PR branch. (optional but recommended, not available for 
branches on forks living under an organisation)
   - [x] I have developed this patch against the `main` branch.
   - [x] I have run `./gradlew check`.
   - [ ] I have added tests for my changes.
   - [ ] I have added documentation for the [Reference 
Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to