Details
Description
When I run-war a trivial application with 1 controller that outputs "hello", I see:
Running Grails application..
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/marc/.ivy2/cache/org.slf4j/slf4j-log4j12/jars/slf4j-log4j12-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/marc/.grails/1.2.0/projects/RunWarTest/war/WEB-INF/lib/slf4j-log4j12-1.5.8.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
Server running. Browse to http://localhost:8080/RunWarTest
Issue Links
- is related to
-
GRAILS-5679
The run-war script is not setting up classpath properly. Even with Ant added to runtime dependencies, errors occur using AntBuilder
-
-
GRAILS-6688
run-war https with Tomcat no longer works
-
- relates to
-
GRAILS-5592
"java.lang.IllegalStateException: Illegal class loader binding" when trying to access jndi: resources
-
For what it's worth, I'm seeing the same issue doing a simple run-app. I did NOT see it until I uninstalled the tomcat plugin & installed the jetty plugin. So the issue may be related to some inconsistency in how the dependencies on those plugins are defined.