dashorst opened a new issue, #1690: URL: https://github.com/apache/wicket/issues/1690
#1684 (GitHub issue #1678) gave `slf4j-simple` test scope in the quickstart archetype. That keeps the back end out of the WAR, but `mvn jetty:run` no longer logs. The jetty-ee11-maven-plugin in the generated pom does not set `useTestScope`, which defaults to `false`, so test-scoped dependencies stay off the webapp classpath. The plugin itself brings only `slf4j-api`. Running `mvn jetty:run` on a freshly generated quickstart now prints ``` SLF4J(W): No SLF4J providers were found. SLF4J(W): Defaulting to no-operation (NOP) logger implementation ``` and all of Wicket's log output, including exceptions logged by the request cycle, is dropped. Before #1684 it appeared on the console. Setting `<useTestScope>true</useTestScope>` in the plugin configuration brings `slf4j-simple` back for `jetty:run`, while the WAR still contains no back end. The comment above the dependency, `<!-- LOGGING DEPENDENCIES - SLF4J-SIMPLE -->`, still presents `slf4j-simple` as the project's logging setup. It should say that it only serves `Start`, `jetty:run` and the tests, and that a WAR deployed to a container without an SLF4J back end of its own (Tomcat, a standalone Jetty) needs one added. The fix also goes to `wicket-10.x` together with #1684, which has not been cherry-picked there yet. -- 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]
