Uploaded image for project: 'WildFly Elytron'
  1. WildFly Elytron
  2. ELY-2190

Bundled jboss-logging classes create conflict

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 1.16.0.Final
    • None
    • None
    • Undefined

      I make sure there are no duplicate classes on the classpath using relevant maven module. When switching our EJB client project which uses wildfly-ejb-client-bom to version 24.0.0.SP1 (.Final too) it pulled wildfly-elytron version 1.16.0.Final (.CR1 with .Final) and caused the following validation error:

      [WARNING] Found duplicate and different classes in [org.jboss.logging:jboss-logging:3.4.2.Final, org.wildfly.security:wildfly-elytron:1.16.0.Final]:
[WARNING]   org.jboss.logging.Log4j2Logger
[WARNING]   org.jboss.logging.LoggerProviders
[WARNING] Found duplicate classes/resources in compile classpath.
[WARNING] Found duplicate and different classes in [org.jboss.logging:jboss-logging:3.4.2.Final, org.wildfly.security:wildfly-elytron:1.16.0.Final]:
[WARNING]   org.jboss.logging.Log4j2Logger
[WARNING]   org.jboss.logging.LoggerProviders
[WARNING] Found duplicate classes/resources in test classpath.

      Were the classes the same there would be no problem really (just add to ignored), but they're different versions. Why bundle anyway?

              Unassigned Unassigned
              d.lepczynski@bossa.pl Dominik Lepczyński (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: