Explain how to configure logback
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the logging topic at https://www.dita-ot.org/dev/topics/logging.html and review the linked Logback configuration documentation. Add an example showing how to place a custom logback.xml on the classpath with higher priority than the default, and verify that the documentation clearly explains how it overrides the default settings.
Written by the indexing model from the issue text.
Description
Description
The topic logging explains how to configure FOP logging with logback. It would be great to find an example here of how to add a custom logback.xml file to the classpath.
To enable debug logging, modify the config/logback.xml file or add your own logback.xml to the classpath with a higher priority to override the default settings. For more information, see the Logback configuration documentation.
- Dominant language
- XSLT
- Stars
- 64
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 dita-ot/docs
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
coverage feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
Similar issues
-
area: docs difficulty: easy documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
manuscript-lang/manuscript#198 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-acceptance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
vllm-project/semantic-router#5002 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
.NET Azure Functions Docs OpenTelemetry
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getsentry/sentry-dotnet#5715 · 1 comment ·
Maintainers usually reply within 2 days