Minor Upstream and downstream slf4j-jboss-logmanager used dev mode for gradle projects, thus SLF4J warning is printed.
Gradle support is not the focus for RHBQ, thus the priority is minor. We still track that as this was discovered during RHBQ 2.2.5. work.
Reproducer:
quarkus create app app --gradle cd app quarkus dev
Listening for transport dt_socket at address: 5005 SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/rsvoboda/.m2/repository/org/jboss/slf4j/slf4j-jboss-logmanager/1.1.0.Final-redhat-00001/slf4j-jboss-logmanager-1.1.0.Final-redhat-00001.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/rsvoboda/.m2/repository/org/jboss/slf4j/slf4j-jboss-logmanager/1.1.0.Final/slf4j-jboss-logmanager-1.1.0.Final.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Slf4jLoggerFactory] __ ____ __ _____ ___ __ ____ ______ --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \ --\___\_\____/_/ |_/_/|_/_/|_|\____/___/ 2022-02-15 14:10:32,891 INFO [io.quarkus] (Quarkus Main Thread) app 1.0.0-SNAPSHOT on JVM (powered by Quarkus 2.2.5.Final-redhat-00010) started in 2.084s. Listening on: http://localhost:8080 2022-02-15 14:10:32,910 INFO [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated. 2022-02-15 14:10:32,911 INFO [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, resteasy, smallrye-context-propagation] 2022-02-15 14:13:03,095 INFO [io.quarkus] (Shutdown thread) app stopped in 0.021s
The reason for that is probably the fact that upstream version of gradle plugin is used => slf4j-jboss-logmanager-1.1.0.Final.jar gets into dep tree. slf4j-jboss-logmanager-1.1.0.Final-redhat-00001.jar is used by supported artifacts.