[
https://issues.apache.org/jira/browse/SOLR-17202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069155#comment-18069155
]
Christos Malliaridis commented on SOLR-17202:
---------------------------------------------
Let me add my two cents too. I believe that putting solrj artifacts into a
separate group could be less intuitive, as it is still part of the same
project. I would personally prefer solrj sub-modules being prefixed with just
{{solrj-}}, instead of {{solr-solrj-}}, like for example
{{org.apache.solr:solrj-core}}.
Why would we otherwise prefix all our modules with {{solr-}}?
> Change SolrJ maven coordinates (10.x)
> -------------------------------------
>
> Key: SOLR-17202
> URL: https://issues.apache.org/jira/browse/SOLR-17202
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: Jan Høydahl
> Priority: Major
>
> Today SolrJ uses the same groupID as Solr itself, {{{}org.apache.solr{}}}.
> In SOLR-16078 [~houston] mentioned that we might need to change groupID for
> SolrJ if we wanted to have a new solrj-core artifact, since Gradle would
> conflate solr-core and solrj-core. Thus in that issue it was
> discussed/concluded to move solrj to {{{}org.apache.solr.solrj{}}}.
> This JIRA is dedicated to that task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
