Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12300 Convert to Jakarta EE 8 specification APIs
  3. WFLY-12490

Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed

    XMLWordPrintable

Description

    The Jakarta related component upgrades which changed groupId and/or artifactId of spec artifacts should be propagated to BOMs and Quickstarts projects.

    Attachments

      Issue Links

        blocks

        Sub-task - The sub-task of the issue WFLY-12468 Rename BOMs artifactIds with javaee8-* to jakartaee8-*

        • 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 blocked by

        Sub-task - The sub-task of the issue WFLY-12442 Upgrade jboss-saaj-api and saaj-impl from 1.3 to 1.4

        • 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

        Sub-task - The sub-task of the issue WFLY-12501 Migrate javax.json to jakarta.json

        • 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

        Sub-task - The sub-task of the issue WFLY-12499 Move javax.json.bind to jakarta.json.bind

        • 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

        Sub-task - The sub-task of the issue WFLY-12502 Move to jakarta.inject:jakarta.inject-api

        • 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

        Sub-task - The sub-task of the issue WFLY-12523 Move javax.validation to jakarta.validation

        • 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

        Sub-task - The sub-task of the issue WFLY-12524 Move com.sun.mail:javax.mail to com.sun.mail:jakarta.mail-api

        • 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
        is related to

        Task - Represents a small unit of work that is not end-user facing. WINDUPRULE-396 JBoss EAP 7.3: Move to Jakarta EE Maven Artifacts

        • 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. JBEAP-17830 Migration Guide section about jakarta maven artifacts replacing 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.
        • Closed
        relates to

        Sub-task - The sub-task of the issue WFLY-12418 Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

        • 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

        Sub-task - The sub-task of the issue WFLY-12418 Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

        • 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

        Sub-task - The sub-task of the issue WFLY-12480 Switch from javax.persistence:javax.persistence-api to jakarta.persistence:jakarta.persistence-api

        • 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

        Sub-task - The sub-task of the issue WFLY-12528 Upgrade CDI dependency to the one from Jakarta

        • 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

        Sub-task - The sub-task of the issue WFLY-12540 Move from javax.activation:activation:1.1.1 to com.sun.activation:jakarta.activation:1.2.1

        • 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

        Task - Represents a small unit of work that is not end-user facing. WFCORE-4648 Migrate javax.json to jakarta.json

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-12460 Upgrade jboss-transaction-api_1.2_spec to jboss-transaction-api_1.3_spec 2.0.0CR1

        • 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

        Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-12460 Upgrade jboss-transaction-api_1.2_spec to jboss-transaction-api_1.3_spec 2.0.0CR1

        • 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:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: