Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-7944

Jersey 1.14 and 1.5 jars mixed in lib with Jersey 1.19

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 17.0.0
    • Fix Version/s: 17.0.0
    • Component/s: Build / Packaging
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Centos 7 Java JDK 8 OpenNMS 17.0.0 snapshot installed from rpm

      Description

      The build system creates a lib directory containing a mix of incompatible Jersey versions:
      jersey-core-1.14.jar, jersey-json-1.14.jar, jersey-apache-client-1.14.jar, jersey-client-1.5.jar
      along side
      jersey-server-1.19.jar, jersey-spring-1.19.jar, jersey-atom-1.19.jar, jersey-multipart-1.19.jar, jersey-servlet-1.19.jar etc.

      The jersey 1.14 problem appears to be in the new
      OpenNMS Features Resource CLI tool module pom.xml
      which calls in hard wired jersey 1.14 dependencies which overwrite the OpenNMS Dependencies Jersey module which has been updated to Jersey 1.19

      Also the OpenNMS Features JIRA Trouble Ticketer
      calls in jersey-client 1.5 and :jersey-apache-client 1.5

      I'm not sure of the overall effect of this but definitely having a mix of Jersey versions in the base class path prevents any jersey rest code from running in the Karaf container.

        Attachments

          Activity

            People

            • Assignee:
              j-white Jesse White
              Reporter:
              cgallen Craig Gallen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: