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

Rename BOMs artifactIds with javaee8-* to jakartaee8-*

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Blocker
    • 18.0.0.Final
    • None
    • BOM, Quickstarts
    • None
    • Documentation (Ref Guide, User Guide, etc.)

    Description

      The following WildFly BOM artifactIds should be renamed to not include javaee, replacing it with jakartaee8:

      • wildfly-javaee8
      • wildfly-javaee8-with-tools

      Reference to renamed BOMs in Quickstarts project should also be updated.

      Attachments

        Issue Links

          is blocked by

          Sub-task - The sub-task of the issue WFLY-12490 Upgrade BOMs and QS due to spec artifacts which groupId/artifactId changed

          • 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. 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-17718 Jakarta EE bom update needed at EAP Developer and Migration Guides

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEE-246 Jakarta EE BOMs

          • 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.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: