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

Remove tanukisoftware wrapper dependency from EAP6 profile

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.0.0.M4
    • 4.17.4
    • Build System
    • None

    Description

      Currently we have tanuki in these components:

      ArjunaCore/arjuna/services/pom.xml
ArjunaJTS/narayana-jts-idlj/pom.xml
ArjunaJTS/narayana-jts-jacorb/pom.xml
pom.xml

          <dependency>
      <groupId>tanukisoft</groupId>
      <artifactId>wrapper</artifactId>
      <version>${version.tanukisoft}</version>
    </dependency>

      We need to remove these dependencies from eap6 profile according to comments from Fernando:

      We do not ship tanukiwrapper with the AS (the windows on is an exceptional case and for different reasons).

      It is not in the AS7 dependencies, and it will be hard for Support to
      properly rebuild TS in the field.

      btw, there are two classes we need to remove from eap6 profile which depends on tanuki wrapper:

      ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java
ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java

      Attachments

        Issue Links

          is cloned by

          Feature Request - Feature requests from customers and/or users JBTM-1689 "jta" vs. "jts" profile seems duplicate

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

          Feature Request - Feature requests from customers and/or users JBTM-1663 JBossTS - EAP6 productization issue tracker

          • 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

              thjenkin@redhat.com Tom Jenkinson
              weinanli Weinan Li
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: