Shiro reports an error

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder“.

Reason found after search:

Logging implication loading org.slf4j.impl.StaticLoggerBinder class failed
This warning message is reported when running the “org.slf4j.impl. Unable to load StaticLoggerBinder class into memory. This happens when a suitable SLF4J binding cannot be found on the class path. Putting one (and only one) of slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar, or logback-classic.jar on the class path should solve the problem.
Note that the slf4j-api version is 2.0. x and later using the ServiceLoader mechanism. Backends, such as logback 1.3 and later, target slf4j-api 2. Do not distribute with org.slf4j.impl.StaticLoggerBinder. If you set up a logging backend targeting slf4j-api 2.0. X, you need to install slf4j-api-2.x.jar on the class path. See the related faq entry.

Solution:
Remove one of the jar packages slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar, leaving only one
runs successfully