Re: OpenAPI: Swagger2 or Swagger3

2017-12-21 Thread Sergey Beryozkin
Sure. I've just really asked for my own understanding in case I talk about it somewhere. Indeed, referring to OpenAPI v3 as Swagger 3 (as opposed to 2) is right, the lib versions is an impl detail... Romain, FYI, Andriy has already provided an initial impl of the OpenAPiFeature based on the

Re: OpenAPI: Swagger2 or Swagger3

2017-12-21 Thread Andriy Redko
It is confusing indeed, for OpenApi v3 integration we decided to get rid of "Swagger" and make the emphasize on OpenApi aspect of it. Swagger 2 is the spec version (2.0) while the 1.5.x is the implementation of it (so we are really naming after the specification). To make things cleaner, we

Re: OpenAPI: Swagger2 or Swagger3

2017-12-21 Thread Dennis Kieselhorst
> Swagger 2 is a bit confusing, given that we have am Open Api version 3 > and the existing Swagger2Feature. We should rely on the versions of the Open API spec which is 2.0 for the original Swagger and 3.0.0 for OpenAPI. swagger-core/ jaxrs 1.5.x deals with spec 2.0 and swagger-core/ jaxrs

Re: OpenAPI: Swagger2 or Swagger3

2017-12-21 Thread Romain Manni-Bucau
+1 for 3 - but not sure java lib is ready Le 21 déc. 2017 13:19, "Sergey Beryozkin" a écrit : > Hi > > How should CXF position its OpenAPI feature, as Swagger 2 or 3 ? > > Swagger 2 is a bit confusing, given that we have am Open Api version 3 > and the existing

OpenAPI: Swagger2 or Swagger3

2017-12-21 Thread Sergey Beryozkin
Hi How should CXF position its OpenAPI feature, as Swagger 2 or 3 ? Swagger 2 is a bit confusing, given that we have am Open Api version 3 and the existing Swagger2Feature. I know Swagger2Feature depends on swagger core/jaxrs 1.5.x, but it is still Swagger2 ? Sergey