Grzegorz Grzybek created CXF-7948: ------------------------------------- Summary: Upgrade to asm 7 Key: CXF-7948 URL: https://issues.apache.org/jira/browse/CXF-7948 Project: CXF Issue Type: Wish Reporter: Grzegorz Grzybek
I just run all tests in 3.2.x-fixes branch with this patch: {noformat} diff --git a/parent/pom.xml b/parent/pom.xml index 234bcbaa0f..47a3885db0 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -47,8 +47,8 @@ <!-- stuff related to ASM --> <cxf.asm.groupId>org.ow2.asm</cxf.asm.groupId> <cxf.asm.artifactId>asm</cxf.asm.artifactId> - <cxf.asm.version>5.2</cxf.asm.version> - <cxf.osgi.asm.version>[3.0,6.3)</cxf.osgi.asm.version> + <cxf.asm.version>7.0</cxf.asm.version> + <cxf.osgi.asm.version>[3.0,8)</cxf.osgi.asm.version> <!-- OSGi related properties --> <cxf.fragment.host /> <cxf.bundle.activator /> {noformat} all tests pass. background: I've prepared _simultaneous_ release of pax-web, pax-transx, pax-jms, pax-jdbc, pax-cdi, preparing for aligned release of karaf 4.2.3. In pax-web I've upgraded to ASM7, so now, pax-web ship/install ASM7 bundles. Karaf itself switched to ASM7 some time ago, but the reason why (so far) CXF tests worked was that pax-web used in Karaf was installing ASM6 libraries. CXF contains (very) wide range for ASM import: {{[3, 6.3)}} and knowing the good history of backward compatibility of ASM, I think it's worth increasing the range for ASM in CXF. -- This message was sent by Atlassian JIRA (v7.6.3#76005)