Are slf4j-api and slf4j-jdk14 jars still needed in v5?

XMLWordPrintable

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: container
    • None

      These are in the Tomcat lib directory:

      • 41513 May 29 07:31 /opt/tomcat/lib/slf4j-api-1.7.32.jar
      •  8490 May 29 07:31 /opt/tomcat/lib/slf4j-jdk14-1.7.32.jar

      These give startup warnings in Grouper.

      grouper_1   | SLF4J: Class path contains multiple SLF4J bindings.
      grouper_1   | SLF4J: Found binding in [jar:file:/opt/grouper/grouperWebapp/WEB-INF/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      grouper_1   | SLF4J: Found binding in [jar:file:/opt/tomcat/lib/slf4j-jdk14-1.7.32.jar!/org/slf4j/impl/StaticLoggerBinder.class]
      grouper_1   | SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
      grouper_1   | SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
      

      They are not natively in the Tomcat lib directory, it's the image build inserting them. SLF4J is used in a few classes in the Grouper module, but that may be accidental. It may be needed by other subprojects or libraries.

            Assignee:
            Chris Hyzer (upenn.edu)
            Reporter:
            Chad Redman
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: