dashorst opened a new issue, #1678:
URL: https://github.com/apache/wicket/issues/1678
The quickstart archetype adds `org.slf4j:slf4j-simple` at compile scope
(`archetypes/quickstart/src/main/resources/archetype-resources/pom.xml`), so
every generated project packages an SLF4J back end in its WAR.
Application servers that bring their own SLF4J back end, such as WildFly,
then
see two back ends: SLF4J warns about it at startup, and the application's
logging may bypass the server's logging configuration. The old quickstart
wizard on the website worked around a similar problem for the Wicket 7
archetype (`-Dlog4j.properties=wildfly-doesnt-need-log4j.properties`).
The back end is only needed by `Start`, which runs Jetty from the test
sources,
and by the tests. Jetty, `wicket-tester` and JUnit already have test scope,
so
`slf4j-simple` can follow:
```xml
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>${slf4j.version}</version>
<scope>test</scope>
</dependency>
```
The WAR then leaves the choice of logging back end to the server or the
application, and `Start` keeps logging during development.
--
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]
