[
https://issues.apache.org/jira/browse/SOLR-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17366391#comment-17366391
]
David Smiley commented on SOLR-15488:
-------------------------------------
I'd rather not see "api" sub-packages because of the reason you saw -- java
package visibility. And as you know I'm a fan of the APIs containing the meat
of the implementation. Over time I hope this trend may continue as these may
stand alone and v1 might map on top of it instead of the other way around.
Thanks for looking into the whole matter though.
> Unify package structure for v2 APIs
> -----------------------------------
>
> Key: SOLR-15488
> URL: https://issues.apache.org/jira/browse/SOLR-15488
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: v2 API
> Affects Versions: main (9.0)
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, V2 APIs are scattered throughout solr-core's package structure.
> Some live in feature-specific packages (e.g. {{PackageAPI}} in
> {{org.apache.solr.pkg}}). Some live alongside v1 "handler" code
> ({{ClusterAPI}} in {{org.apache.solr.handler}}), or in a feature specific
> package below that ({{ZookeeperReadAPI}} in
> {{org.apache.solr.handler.admin}}). Some (the most recently created), live
> in a package intended for v2 APIs within the "handler" package (e.g.
> {{AddReplicaPropertyAPI}} in {{org.apache.solr.handler.admin.api}}).
> We should decided on the best place(s) for these classes to live, and realign
> them accordingly so that the convention is clear for future work on the v2
> APIs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
