Details

    • Story
    • Resolution: Duplicate
    • Major
    • 2.5.0.Final
    • None
    • EAP6 -> EAP7
    • None
    • Sprint 37

    Description

      From JBoss EAP 7.1 Migration Guide:

      "5.3.3. Replace the HornetQ API
      JBoss EAP 6 included the org.hornetq module, which allowed you to use the HornetQ API in your application source code.

      Apache ActiveMQ Artemis replaces HornetQ in JBoss EAP 7, so you must migrate any code that used the HornetQ API to use the Apache ActiveMQ Artemis API. The libraries for this API are included in the org.apache.activemq.artemis module.

      ActiveMQ Artemis is an evolution of HornetQ, so many of the concepts still apply."

      A new RHAMT Rule should be added to address this app migration issue.
      When: app uses/references "org.hornetq" package (or children)
      Perform: alert the user that the JBoss EAP 7 does not supports HornetQ API, that application should use Apache ActiveMQ Artemis API instead.

      Attachments

        Issue Links

          Activity

            People

              mnovotny@redhat.com Marek Novotny
              emartins@redhat.com Eduardo Martins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: