Uploaded image for project: 'WildFly Transaction Client'
  1. WildFly Transaction Client
  2. WFTC-144

wildfly-transaction-client depends on the org.wildfly.security:wildfly-elytron shaded artifact

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • None
    • Critical

      WildFly components must not depend on org.wildfly.security:wildfly-elytron uber-artifact. Please work with the Elytron team to identify the specific Elytron artifacts that are needed and add dependencies on those instead.

      WildFly Transaction Client is a client-side artifact so it can't depend on the server's modular classloading to prevent irrelevant types being exposed. People who depend on wildfly-transaction-client can end up pulling in org.wildfly.security:wildfly-elytron, which in turn shades in a bunch of classes from external artifacts. We don't want our users having to deal with that. Hence it is banned.

      This org.wildfly.security:wildfly-elytron dep ends up in the org.wildfly:wildfly-ejb-client-bom, where it is causing problems.

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

                Created:
                Updated: