[
https://issues.apache.org/jira/browse/SOLR-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017543#comment-18017543
]
David Smiley commented on SOLR-17884:
-------------------------------------
* Utils.java: has utility methods for Apache HttpClient. These can go to
HttpClientUtil.
* build.gradle: use "implementation" instead of "api" scope to subdue it's
exposure. Already so on 10 but should be brought to 9.
* HttpClientUtils: constants that are generic should go to some new class;
maybe a "SolrClientConstants" (maybe with "Http"); or maybe bring to SolrClient
itself since in practice, any user is going to use an Http oriented client
anyway.
The scope here does not include solrj-streaming, which in 9.x continues to have
Apache HttpClient specific code. ":solr:api" is already free of this
dependency, as is ":solrj-zookeeper".
> SolrJ should be usable without Apache HttpClient dependencies
> -------------------------------------------------------------
>
> Key: SOLR-17884
> URL: https://issues.apache.org/jira/browse/SOLR-17884
> Project: Solr
> Issue Type: Improvement
> Components: SolrJ
> Reporter: David Smiley
> Priority: Major
>
> The SolrJ JAR, with either JDK or Jetty based HttpClient, should be usable
> without the Apache HttpClient dependency being on the classpath. But Apache
> HttpClient has been used in SolrJ for so long that it has some unanticipated
> tentacles. This JIRA intends to go to Solr 9 (as well as 10 of course).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
