swagger-1.5.10-SNAPSHOT is available at the sonatype snapshot repo https://oss.sonatype.org/content/repositories/snapshots see https://oss.sonatype.org/content/repositories/snapshots/io/swagger/swagger-core
2016-07-31 8:34 GMT+02:00 Niten Aggarwal <[email protected]>: > Hi Andriyo, > > As per your last comment in https://issues.apache.org/jira/browse/CXF-6740 > you mentioned, > > Tested against Swagger 1.5.10-SNAPSHOT, the issue has been mitigated. > Updated OSGI sample: jax_rs/description_swagger2_osgi > > I am also trying to test same using 1.5.10-SNAPSHOT but not able to figure > out how to pass usePathBasedConfig with Swagger2Feature. I think as per > https://github.com/swagger-api/swagger-core/pull/1656 usePathBaseConfig has > to be set to true to scan base resource. As 1.5.10 has not release in > central, how did you tested this with snapshot version? > > <!-- CXF Swagger2Feature --> > <bean id="swagger2Feature" > class="org.apache.cxf.jaxrs.swagger.Swagger2Feature"> > <property name="basePath" value="/cxf/swaggerSample"/> > <property name="usePathBasedConfig" value="true" /> > </bean> > > Thanks, > Niten Aggarwal > > -----Original Message----- > From: Sergey Beryozkin [mailto:[email protected]] > Sent: Tuesday, July 26, 2016 12:22 AM > To: [email protected] > Subject: Re: Collision by Swagger2Feature in two OSGI bundles > > Hi > > No, because Swagger core 1.5.10 has not been released yet > > Sergey > On 26/07/16 01:32, Niten Aggarwal wrote: >> Hi Sergey, >> >> >> >> Could you please let me know if >> https://issues.apache.org/jira/browse/CXF-6740 ticker got pushed to central >> repository and if yes with what version. >> >> PR to Swagger had been submitted: >> https://github.com/swagger-api/swagger-core/pull/1656 >> >> >> >> Thanks, >> Niten Aggarwal >> >> >> >> ::DISCLAIMER:: >> ---------------------------------------------------------------------- >> ---------------------------------------------------------------------- >> -------- >> >> The contents of this e-mail and any attachment(s) are confidential and >> intended for the named recipient(s) only. >> E-mail transmission is not guaranteed to be secure or error-free as >> information could be intercepted, corrupted, lost, destroyed, arrive >> late or incomplete, or may contain viruses in transmission. The e mail and >> its contents (with or without referred errors) shall therefore not attach >> any liability on the originator or HCL or its affiliates. >> Views or opinions, if any, presented in this email are solely those of >> the author and may not necessarily reflect the views or opinions of >> HCL or its affiliates. Any form of reproduction, dissemination, >> copying, disclosure, modification, distribution and / or publication of this >> message without the prior written consent of authorized representative of >> HCL is strictly prohibited. If you have received this email in error please >> delete it and notify the sender immediately. >> Before opening any email and/or attachments, please check them for viruses >> and other defects. >> >> ---------------------------------------------------------------------- >> ---------------------------------------------------------------------- >> -------- >> >
