This looks like a symptom of having multiple versions of the same dependency (slf4j) in your classpath.
Look in your logs for this message:
SLF4J: Class path contains multiple SLF4J bindings.
It will default to using the first slf4j reference it finds in the classpath. In the past, I've fixed this by moving my Logback dependencies (logback-classic and logback-core) to the top of the dependencies section of my Maven pom.xml file, which places them earlier in the classpath. That's a fragile solution, and it may not work depending on your application architecture. (e.g. if your startup project contains the conflicting dependency in its pom.xml, and you reference Logback through another project and its pom.xml)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…