[
https://issues.apache.org/jira/browse/SOLR-15342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17485352#comment-17485352
]
Houston Putman commented on SOLR-15342:
---------------------------------------
Thanks for the PR [~haythemkh] !
I may be alone on this, but given that this is not the only solrj module that
we are trying to create, maybe we create modules as sub-directories of
{{{}solrj/{}}}, such as:
* {{solr/sorlj/core}}
* {{solr/solrj/zookeeper}}
* {{solr/solrj/jdbc}}
* {{solr/solrj/streaming}}
etc.
We can create one artifact that inherits all of these,
{{{}solr-solrj-<version>.jar{}}}, and name all others
{{{}solr-solrj-<module>-<version>.jar{}}}. I'm sure I've seen this opinion
somewhere, but my quick search doesn't bring anything up.
Anyways, I think this would keep the repository a lot cleaner now that we have
more directories under {{{}solr/{}}}.
> Separate out a SolrJ-Zookeeper module
> -------------------------------------
>
> Key: SOLR-15342
> URL: https://issues.apache.org/jira/browse/SOLR-15342
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: David Smiley
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Let's create a new "SolrJ-Zookeeper" module by refactoring out the ZooKeeper
> related code out of the existing SolrJ module. This allows clients that
> don't want to talk to ZooKeeper to use the SolrJ module without transitive
> dependencies for ZooKeeper or Netty (Netty is used by ZK for SSL).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
