[
https://issues.apache.org/jira/browse/SOLR-17202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828519#comment-17828519
]
David Smiley commented on SOLR-17202:
-------------------------------------
Either both the group and artifact ID stay the same, or we change either/both &
do the pom.xml relocation thing to help users with the transition.
My point above is mostly that this isn't a change that is particularly
compelling. org.apache.solr:solr-solrj isn't ugly or confusing. The "solr"
prefix is a bit redundant.
If we decide to make a change, we don't need a "-core" suffix; it's
core-ness/centrality is implied with simply a "solrj" artifactID.
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
