Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17218

The jboss-client jar should not shade JBoss Log Manager

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 27.0.0.Final
    • None
    • EJB, Logging
    • None

    Description

      The WFLY-17209 fix breaks the TCK badly because it adds JBoss Log Manager into the jboss-client jar.

      If a client application wants to take advantage of JBoss Log Manager it should declare that itself; the jboss-client jar should not impose that choice on it.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-17209 jboss-client.jar is missing jboss-modules classes which are required by jboss-ejb-client

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-24130 [GSS](7.4.z) WFLY-17209 - jboss-client.jar is missing jboss-modules classes which are required by jboss-ejb-client

          • 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

              bstansbe@redhat.com Brian Stansberry
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: