swagger-api / swagger-api/swagger-codegen
[Java]: >3.0.20 spring logging broken
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
A working spring boot app (say, based on spring-boot-starter-parent 2.3.4.FINAL) and with a working swagger codegen <=3.0.20 will produce application logs as expected. When upgrading to swagger codegen 3.0.21 (or x.x.22), application is no longer able to generate logs.
Swagger-codegen version
Spring logging works w/: codegen <= 3.0.20
Spring logging is broken w/: codegen: 3.0.21, 3.0.22
Steps to reproduce
Take any working spring boot app with swagger codegen (<=3.0.20) and upgrade to a newer version (x.x.21 or x.x.22).
Contributor 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.
Research direction
Start by reproducing the issue with a Spring Boot app using swagger-codegen 3.0.20, then upgrade to 3.0.21 and 3.0.22 and compare the generated application's logging behavior and dependencies. Done means application logs are produced after upgrading to the affected codegen versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100