Quickstart archetype: give slf4j-simple test scope
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- backend, build-system
Research direction
In archetypes/quickstart/src/main/resources/archetype-resources/pom.xml, find the org.slf4j:slf4j-simple dependency and set its scope to test. Check that the generated project keeps this backend available to Start and tests while leaving it out of the WAR; the issue identifies the expected dependency change.
Written by the indexing model from the issue text.
Description
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:
<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.
- Dominant language
- Java
- Stars
- 797
- Forks
- 416
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 36
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/wicket
-
COOP and COEP exemptions compare with the context path, so page exemptions never matchPossibly taken @VelpulaGangavardhan claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
apache/wicket#1661 · 1 comment ·
Maintainers usually reply within 1 day
-
The CSP report-uri is lost in development mode because strict() clears itPossibly taken @VelpulaGangavardhan claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/wicket#1660 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/wicket#1567 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 71/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
apache/rocketmq-dashboard#6896 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenIntegrationEngine/engine#496 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SasanLabs/VulnerableApp#836 ·
Maintainers usually reply within 1 day
-
enhancement frontend
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Albertinesilva/backend-engineering-journey-java-springboot#46 ·
-
Snyk: vulnerabilities in jackson-databind 2.21.5Possibly taken @harrywu23 claimed this today. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
SOFTENG-310-Group-4/Project-A1-310-Group-4#115 ·
Maintainers usually reply within 1 day