You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by "dashorst (via GitHub)" <gi...@apache.org> on 2026/10/20 07:07:05 UTC
[I] Quickstart: mvn jetty:run has no SLF4J back end after slf4j-simple moved to test scope [wicket]
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: dev-unsubscribe@wicket.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Quickstart: mvn jetty:run has no SLF4J back end after slf4j-simple moved to test scope [wicket]
Posted by "Vis-halV (via GitHub)" <gi...@apache.org>.
Vis-halV commented on issue #1690:
URL: https://github.com/apache/wicket/issues/1690#issuecomment-6291474779
I moved slf4j-simple to test scope to prevent it from being bundled in the WAR. I hadn't thought about what would happen when deploying to a servlet container without its own SLF4J backend.
In that case, the developer would need to add one.
--
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: dev-unsubscribe@wicket.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Quickstart: mvn jetty:run has no SLF4J back end after slf4j-simple moved to test scope [wicket]
Posted by "martin-g (via GitHub)" <gi...@apache.org>.
martin-g commented on issue #1690:
URL: https://github.com/apache/wicket/issues/1690#issuecomment-6285559923
A vague memory tells me this was the idea of using compile scope for slf4j-simple - it is up to the developer to evolve the quickly generated app (the quickstart) to his/her needs, e.g. by replacing slf4j-simple with whatever (s)he prefers. But the quickstart should work out of the box in any environment.
AFAIR even the Shell command generator in the website had logic like "any container but Wildfly" again related to logging setup.
What happens now when the developer deploys the .war to a non-embedded servlet container ?
--
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: dev-unsubscribe@wicket.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org