JakeWharton / JakeWharton/multiproject-refactors
Add version constraints to multi-artifact Gradle module metadata
- Dominant language
- No language data
- Stars
- 9
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
BOMs suck. Gradle lets us automatically constrain sibling dependencies to have versions which match, so let's do that.
External requests:
* https://github.com/square/okhttp/issues/9084
Projects:
* [ ] `JakeWharton/diffuse`
* [ ] `JakeWharton/mosaic`
* [ ] `JakeWharton/RxReplayingShare`
* [ ] `JakeWharton/RxWindowIfChanged`
* [ ] `lysine-dev/okio`
* [ ] `lysine-dev/okhttp`
* [ ] `lysine-dev/retrofit`
* [ ] `SQLDelight/SQLDelight`
* [ ] `square/kotlinpoet`
* [ ] `square/zstd-kmp`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked external request at JakeWharton/okhttp#9084 and review the project checklist in this issue. Done means implementing matching sibling-dependency version constraints in the Gradle module metadata for the listed projects and checking off each completed project.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100