swagger-api / swagger-api/swagger-codegen
DISCUSSION :: Should we use maven-checkstyle to enforce Java coding style?
Open
Nobody has claimed this yet.
General: Suggestion
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Our code is mostly formatted according to Google Java Style, but we can enforce this pretty easily using maven-checkstyle: https://maven.apache.org/plugins-archives/maven-checkstyle-plugin-2.16/
Swagger-codegen version
All.
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 reviewing the issue discussion and the linked Maven Checkstyle plugin documentation. The payload names no repository files, entry points, or tests, so locate the project’s build configuration before deciding how enforcement would apply across all generated code. Done means the project has an agreed, reproducible Java-style enforcement approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100