Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-7948

Upgrade to asm 7

    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.2.8, 3.3.0
    • None
    • None
    • Unknown

    Description

      I just run all tests in 3.2.x-fixes branch with this patch:

      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 />
      

      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.

      Attachments

        Activity

          People

            ffang Freeman Yue Fang
            ggrzybek Grzegorz Grzybek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: