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

Upgrade Apache httpcore and httpclient

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 20.1.0
    • Fix Version/s: 21.0.0
    • Component/s: Architecture
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Sprint:
      Horizon - September 27th

      Description

      For a custom development project (provide an implementation to support Amazon SQS instead of ActiveMQ/Kafka for the RPC/Sink patterns to communicate with Minions), it is required to support Httpclient 4.5.x (to be more precise, 4.5.2) and Httpcore 4.4.x (to be more precise 4.4.4), as these two libraries are required by another library (a.k.a. aws-java-sdk-core) which is the core of the new integration we would like to have in OpenNMS.

      Currently, OpenNMS supports Httpclient 4.3.6 and Httpcore 4.3.3.

      Here is the preliminary list of OpenNMS components that rely on Httpclient (based on current develop).

      External Dependencies

      • org.apache.activemq:activemq-http:5.4.15
      • org.apache.thrift:libthrift:jar:0.9.2
      • org.springframework.security.kerberos:spring-security-kerberos-client:1.0.1
      • com.atlassian.jira:jira-rest-java-client-core:3.0.0
      • io.searchbox:jest:jar:2.0.3
      • com.github.tomakehurst:wiremock:jar:1.57
      • geoGoogle:geoGoogle:jar:1.5.1-20110518onms1
      • org.seleniumhq.selenium:selenium-remote-driver:jar:2.44.0

      Internal Dependencies

      • org.opennms.core:org.opennms.core.web
      • org.opennms.features.minion:core-impl
      • org.opennms.features.poller.monitors:org.opennms.features.poller.monitors.core
      • org.opennms.features:org.opennms.features.ifttt
      • org.opennms.plugins:opennms-es-rest
      • org.opennms.features:opennms-integration-rt
      • org.opennms.features.vaadin-dashlets:dashlet-grafana
      • org.opennms:opennms-vmware

      The idea would be update the POMs with the new versions, and then fix what it is required to be fixed in OpenNMS.

        Attachments

          Activity

            People

            • Assignee:
              agalue Alejandro Galue
              Reporter:
              agalue Alejandro Galue
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: