[
https://issues.apache.org/jira/browse/CXF-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286671#comment-16286671
]
Andriy Redko commented on CXF-7525:
-----------------------------------
Hi Sergey,
Swagger2Feature is but not Swagger UI. The distribution mode (and the
integration with CXF) did not change at all, and by and large, Swagger UI does
not depend on Swagger itself. The Swagger UI integration functionally hasn't
been changed, I just extracted it into separate module so we could use it
across Swagger2Feature and OpenApiFeature. All we have done before stays
exactly the same. The Swagger UI is able to recognize different specification
format (Swagger 1.0, 2.0, OpenAPI 3.0, ...), the sample I have committed along
with the OpenApiFeature demos that (old samples work the same way). Sure, I
thought it would be good to reuse same code we tested for Swagger 2.x in
OpenApi as well. As I said, functionally I didn't change anything. What do you
think, concerns cleared? :-)
Best Regards,
Andriy Redko
> Add support for Swagger 2.0 (OpenApi Spec 3.0)
> ----------------------------------------------
>
> Key: CXF-7525
> URL: https://issues.apache.org/jira/browse/CXF-7525
> Project: CXF
> Issue Type: Improvement
> Reporter: Andriy Redko
> Assignee: Andriy Redko
>
> The OpenApi spec 3.0 has been released recently. Swagger 2.0 (currently in
> rc-2) should released in a few months (Dec/Jan). It would be great to have
> the integration available in CXF as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
