[ https://issues.apache.org/jira/browse/SOLR-16825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912466#comment-17912466 ]
Jason Gerlowski commented on SOLR-16825: ---------------------------------------- I've mostly tested with IntelliJ, but I'm sure we can get Eclipse working if we have folks to test and maintain that integration. I'll chime in on the dev@ thread you sent this weekend, in the aim of keeping discussion in a single place. > Generate Java bindings from OpenAPI spec > ---------------------------------------- > > Key: SOLR-16825 > URL: https://issues.apache.org/jira/browse/SOLR-16825 > Project: Solr > Issue Type: Improvement > Components: v2 API > Reporter: Jason Gerlowski > Assignee: Jason Gerlowski > Priority: Major > Labels: pull-request-available > Fix For: 9.8 > > Time Spent: 13h 50m > Remaining Estimate: 0h > > SOLR-16346 added support to Solr's build to generate an "OpenAPI spec" file > describing our v2 API. But currently, this spec file isn't actually used by > Solr in any way. > Spec files can be used for a variety of purposes, including to [generate > client bindings|https://github.com/OpenAPITools/openapi-generator] for using > the API. > The client generation capabilities provided by the OpenAPI project cover a > variety of languages, but it make sense for Solr to start with Java since we > already have a Java client that requires continual effort to keep up to date. > It'd be a big win for the project if we were able to replace some or all of > the manually maintained "SolrRequest" implementations in SolrJ with > automatically generated code. -- 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