papegaaij commented on issue #1690: URL: https://github.com/apache/wicket/issues/1690#issuecomment-6771972691
Deploying the WAR to a container without an SLF4J back end of its own, such as Tomcat or a standalone Jetty, gives SLF4J's "No SLF4J providers were found" warning at startup. The application then logs nothing until a back end is added. The other way round, a bundled back end breaks containers that bring their own, like WildFly (#1678). No setup satisfies both. I think this is the right trade-off. The quickstart is run with `mvn jetty:run` or `Start` far more often than it is deployed as is, and both keep logging through `slf4j-simple`. Anyone deploying the WAR to their own container has to choose a logging back end anyway, and SLF4J's warning says clearly what is missing. The comment above the dependency in the generated pom says so, and I'll mention it in the documentation as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
