Uploaded image for project: 'WINDUPRULE - Red Hat Application Migration Toolkit rules'
  1. WINDUPRULE - Red Hat Application Migration Toolkit rules
  2. WINDUPRULE-764

JBoss EAP 6.4/7.x to 8.0 Migration

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Major
    • None
    • None
    • None
    • None
    • JBoss EAP 7.x to 8.0 Migration
    • False
    • False
    • To Do
    • 83
    • 83% 83%
    • Undefined
    • AMM Sprint 228, AMM Sprint 229, AMM Sprint 232, AMM Sprint 231, AMM Sprint 233, AMM Sprint 234, AMM Sprint 235, AMM Sprint 236, AMM Sprint 237

    Description

      The rules should be added to MTA, providing support for the migration of EAP 6.4/7.x apps to EAP 8.0 or later.

      • The sources of the EAP 6.4 -> EAP 8.0+ rules should be placed in the following directory:
        /rules-reviewed/eap8/eap6
        The targetTechnology XML element for the EAP 6.4 -> EAP 8.0+ rules should have the following attribute values:
        id="eap"
        versionRange="[8,)"
      • The sources of the EAP 7.x -> EAP 8.0+ rules should be placed in the following directory:
        /rules-reviewed/eap8/eap7
        The targetTechnology XML element for the EAP 7.x -> EAP 8.0+ rules should have the following attribute values:
        id="eap"
        versionRange="[8,)"

      Attachments

        Issue Links

          clones

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. WINDUPRULE-756 JBoss EAP 7.3 to 7.4 Migration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          incorporates

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. WINDUP-3147 Java EE 8 to Jakarta EE 9 source migration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-951 EAP 8: EJB Client Legacy BOM Removal

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Release Pending

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-1019 EAP 8: Deprecated InitialContext is removed

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Release Pending

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-907 EAP 8: Migrate Maven Dependency Management

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-1018 EAP 8: log4j-jboss-manager removed

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. WINDUP-3128 MTA - javax to jakarta package renaming (Openrewrite)

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUP-3149 Java EE 8 to Jakarta EE9 - Rename deployment descriptor namespaces

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUP-3150 Java EE 8 to Jakarta EE9 - Rename properties prefixed with javax

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUP-3151 Java EE 8 to Jakarta EE9 - Rename bootstrapping files

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Dev Complete

          Task - Represents a small unit of work that is not end-user facing. WINDUP-3148 Java EE 8 to Jakarta EE9 - update pom.xml dependencies

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              emartins@redhat.com Eduardo Martins
              emartins@redhat.com Eduardo Martins
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: