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

Bundled slf4j classes create conflict.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 1.14.1.Final
    • Build
    • None

    Description

      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 22.0.1.Final it pulled wildfly-elytron version 1.14.1.Final and caused the following validation error:

       

      [WARNING] Found duplicate and different classes in [org.slf4j:slf4j-api:1.7.30, org.wildfly.security:wildfly-elytron:1.14.1.Final]:
      [WARNING]   org.slf4j.LoggerFactory
      [WARNING]   org.slf4j.MDC
      [WARNING]   org.slf4j.event.EventConstants
      [WARNING]   org.slf4j.event.EventRecodingLogger
      [WARNING]   org.slf4j.event.Level
      [WARNING]   org.slf4j.helpers.BasicMDCAdapter
      [WARNING]   org.slf4j.helpers.BasicMarker
      [WARNING]   org.slf4j.helpers.BasicMarkerFactory
      [WARNING]   org.slf4j.helpers.MarkerIgnoringBase
      [WARNING]   org.slf4j.helpers.MessageFormatter
      [WARNING]   org.slf4j.helpers.SubstituteLogger
      [WARNING]   org.slf4j.helpers.Util
      

      Please use normal dependency, which can be excluded, rather than bundle slf4j classes into your jar.

       

       

      Attachments

        Issue Links

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              d.lepczynski@bossa.pl Dominik Lepczyński (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: