Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-2917

ee9 branch issues tracking

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Minor
    • None
    • Wanted But Unscheduled
    • jaxrs
    • None
    • Undefined

    Description

      Track remaining tasks for migration to ee9.

      Attachments

        Issue Links

          relates to

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2923 ee9 reenabled tests in arquillian module

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2916 ee9 branch re-enable microprofile-tck test module

          • 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. RESTEASY-2908 bouncycastle jakarta JAR updates cleanup

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2921 ee9 update springframework to versions migrated to jakarta

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2918 ee9 reenable security tests in integration-tests

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2919 ee9 remove galleon transform when appropriate

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2920 ee9 remove ee9 profile when appropriate

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Task - Represents a small unit of work that is not end-user facing. RESTEASY-2922 ee9 remove use of optimus when appropriate

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Activity

            People

              rsearls r searls
              rsearls r searls
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: