Not something to worry about, no. The code resolves to the right
binding to use Log4j2. We just need to add an exclusion to the Maven
files so that the second JAR doesn't get pulled in.
On Sat, Mar 28, 2020 at 5:02 AM Guy Incognito
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
Am getting this message in the cmd window with the latest pre-release build.
Not sure if it’s anything to worry about or not...
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/D:/.scripts/comixed-app-pre-release.jar!/BOOT-INF/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/D:/.scripts/comixed-app-pre-release.jar!/BOOT-INF/lib/log4j-slf4j-impl-2.11.1.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
[ch.qos.logback.classic.util.ContextSelectorStaticBinder]
