maint(android): use Gradle's version catalog for dependencies
- Dominant language
- Pascal
- Stars
- 534
- Forks
- 143
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 113
Description
This would allow to specify the dependency details and versions only once and then reference them from the `build.gradle` files.
There had been a PR already (#16141) but that came at a wrong time of the release cycle so it was decided to do this work at the beginning of v20.
See attached patch.
[0001-chore-android-use-gradle-version-catalog-for-depende.patch](https://github.com/user-attachments/files/29391561/0001-chore-android-use-gradle-version-catalog-for-depende.patch)
Not included in patch, but these `build.gradle` files also need the dependency added:
- `oem/firstvoices/android/app/build.gradle`
- `android/Samples/KMSample1/app/build.gradle`
- `android/Samples/KMSample2/app/build.gradle`
- `android/Tests/KeyboardHarness/app/build.gradle`
Contributor guide
Research direction
Start by reviewing the attached patch and the existing build.gradle files, including oem/firstvoices/android/app/build.gradle, android/Samples/KMSample1/app/build.gradle, android/Samples/KMSample2/app/build.gradle, and android/Tests/KeyboardHarness/app/build.gradle. Confirm the dependency details are defined once through Gradle's version catalog and that all listed Android builds reference the dependency consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, mobile
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100