[
https://issues.apache.org/jira/browse/SOLR-16079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798649#comment-17798649
]
David Smiley commented on SOLR-16079:
-------------------------------------
[~janhoy] your response to my question was not a "no" (or "yes"); it was
something else — where we may be going in the bigger picture, and it makes
sense to me. But my question is about this issue description which I find
confusing (speaking of empty modules). Can't this be?:
{quote}Create a new SolrJ module, solrj-apachehttp, which contains the SolrJ
code that depends on Apache HttpClient. The Apache HttpClient dependencies
should be declared there. solrj will have a dependency on this in Solr 9 but
Solr 10 will not. solr-core will need this dependency (until we make it go
away!), as will tests of some modules.
{quote}
That's what we did for solrj-zookeeper. No empty modules :) Any concerns?
> New solrj-apachehttp module
> ---------------------------
>
> Key: SOLR-16079
> URL: https://issues.apache.org/jira/browse/SOLR-16079
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: Jan Høydahl
> Priority: Major
>
> As the HttpSolrClient based on apache http client will be deprecated in 9.0,
> then the new {{solrj-core}} module does not need to add those in its
> build.gradle. Instead we can make an "empty" module that pulls in those
> dependencies, so that users wanting to use the old client must add that
> dependency. Then in 10.0 we'll remove both the old clients and this jar.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
