Details
-
Task
-
Resolution: Won't Do
-
Critical
-
None
-
None
-
None
Description
FUSEQE-9077 mentions problems that some Fuse 7 BOMs use Validation API 1 and some - Validation API 2 (Hibernate Validator 5 and Hibernate Validator 6 respectively).
https://issues.apache.org/jira/browse/CXF-8151 Upgrades to Validation API 2 in CXF 3.4.0 and it potentially could be backported to "our" CXF in jboss-fuse/cxf fork.
I tried this, but:
- swagger2 (1.5.17) still has OSGi import range for Validation API 1 - but I've fixed this in our fork in https://github.com/jboss-fuse/swagger-core/commits/v1.5.24-fuse-77x
- CXF-8151 also updates swagger3 (2.1.x) to match Validation API 2, but at the same time, this swagger3 2.1.x starts OSGi importing Jackson 2.10+
- I tried downgrading swagger3 to 2.0.x (yes - swagger versioning is ugly), but this brought back requirement on Validation API 1
So in theory, CXF could switch to jackson 2.10+ (some Camel components use this version anyway), but Fuse 7 BOMs provide jackson 2.8 and 2.9 (depending on flavor).
This is PM level decision about jackson, especially because recently we've switched to whitelist-enabled jackson 2.8/2.9.
janstey@redhat.com, gmalinko, jonnychristison, yfang@redhat.com, acosenti FYI ^^^.
Attachments
Issue Links
- relates to
-
ENTESB-13925 Upgrade to Validation API 2 / Hibernate Validator 6
- Resolved