Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3673

JDK17 profile is no longer needed - Arquillian dependencies should be updated instead

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.0.0.CR1
    • None
    • None
    • None

    Description

      Since the update to WildFly 27, the profile jdk17 is not more needed for testing Narayana.

      Edit
      It turns out that this issue has deeper roots than I thought. Since Narayana moved to JDK17, the codebase started using add-opens to include some libraries to run some tests of our testsuite. A better solution should replace this workaround. In fact, the reason why add-opens was employed is because of old Arquillian related dependencies used in Narayana.

      This issue is also connected to WFLY (and Jakarta). WFLY is moving towards Jakarta and EE 10 and, as a consequence, there are many new improvements to import into Narayana (for example, [1][2]). Narayana needs to move towards these two targets ASAP. This JIRA is a prerequisite to this work.

      [1] https://www.wildfly.org/news/2022/05/12/WildFlyPreview27-Alpha1-Released/
      [2] https://weld.cdi-spec.org/news/2022/01/24/weld-500Beta1/

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3670 Make the quickstarts work with JDK17

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3743 Removed add-opens/jdk17 profile from `rts/lra/test/tck/pom.xml`

          • 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

              jfinelli@redhat.com Manuel Finelli
              jfinelli@redhat.com Manuel Finelli
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: