[
https://issues.apache.org/jira/browse/SOLR-16880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741205#comment-17741205
]
Mike Drob commented on SOLR-16880:
----------------------------------
Can you provide more detail about the logistics of this? Would we host it out
of our release svn? Is there a community repository for spec files somewhere?
Are they deterministically reproducible for each source build? Is there a way
to verify that a given spec file actually corresponds to a given specific
artifact?
An alternative approach would be to check in the generated spec to our source
tree.
> Make OpenAPI spec a release artifact
> ------------------------------------
>
> Key: SOLR-16880
> URL: https://issues.apache.org/jira/browse/SOLR-16880
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: v2 API
> Reporter: Jason Gerlowski
> Priority: Major
>
> SOLR-16346 added OpenAPI spec generation to Solr - allowing us to produce a
> detailed description of our v2 APIs (or at least - those APIs implemented
> using JAX-RS).
> These spec files have a lot of potential uses - from generating
> documentation, to API clients, to web UIs. These have a lot of promise, but
> it will take the community time to implement and adopt some of them.
> We should make the OpenAPI spec available as a release artifact, so that
> users can more easily take advantage of it. Having it published on each
> release will also allow us to compare specs across versions, as a way to
> detect backcompat breaks before changes go out the door.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
