consider removing dependency on `com.google.code.findbugs:jsr305`
Open
Nobody has claimed this yet.
area/build
kind/engineering
- Dominant language
- Java
- Stars
- 85
- Forks
- 26
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 22
Description
A community member in slack asked why we depend on com.google.code.findbugs:jsr305
Opening an issue to track the suggested work item.
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 at pkg/codegen/java/package_info.go lines 178-180 and inspect how the com.google.code.findbugs:jsr305 dependency is declared or generated. Trace whether it is still required, then confirm the tracked dependency is removed without leaving the generated Java package metadata inconsistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100