I've reverted back to 1.5.17 as I see systests failing with it.
FYI, tests pass OK with 1.5.18 in 3.1.x which stayed at 1.5.12.
In 3.1.x we retained the the same feature code but on the master, when
upgrading to 1.5.16 (?) we had to change that as the same model did nnot
work anymore. Now it appears 1.5.18 has changed internally to the older
per 1.5.16 model.
IMHO, it only makes sense to move to newer 1.5.x versions when it can
bring something new to the users, rewriting Swagger2Feature with every
swagger-jaxrs/core 1.5.x iteration seems a bit too much :-)
Thanks, Sergey
On 01/02/18 09:33, Sergey Beryozkin wrote:
Hi Dennis
We were looking with Francesco at this version and saw some issues, do
systest/jaxrs tests pass for you ?
Thanks, Sergey
On 01/02/18 09:30, d...@apache.org wrote:
This is an automated email from the ASF dual-hosted git repository.
deki pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cxf.git
The following commit(s) were added to refs/heads/master by this push:
new 2cd77ba update swagger-core to latest version
2cd77ba is described below
commit 2cd77bae06fc51ef2bc6d7679db1fdf6e9476af1
Author: Dennis Kieselhorst <m...@dekies.de>
AuthorDate: Thu Feb 1 10:30:00 2018 +0100
update swagger-core to latest version
---
parent/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/parent/pom.xml b/parent/pom.xml
index 9c80f55..ea4516d 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -159,7 +159,7 @@
<cxf.spring.osgi.version>1.2.1</cxf.spring.osgi.version>
<cxf.spring.ldap.version>2.3.2.RELEASE</cxf.spring.ldap.version>
<cxf.spring.mock>spring-test</cxf.spring.mock>
- <cxf.swagger2.version>1.5.17</cxf.swagger2.version>
+ <cxf.swagger2.version>1.5.18</cxf.swagger2.version>
<cxf.swagger.v3.version>2.0.0-rc4</cxf.swagger.v3.version>
<cxf.swagger.ui.version>3.9.2</cxf.swagger.ui.version>
<cxf.velocity.version>2.0</cxf.velocity.version>
