mapbox / mapbox/mapbox-navigation-android
Gradle dependency management, follow-up of `okhttp` version control #2762
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
**Android API:** 19
**Mapbox Navigation SDK version:** ALL
As follow-up of the comment https://github.com/mapbox/mapbox-navigation-android/pull/2762#discussion_r409893083 in PR #2762
> One thing that we could explore though is publishing a bill of materials (BOM) for our SDKs. Depending on this from Gradle or Maven would keep all of our SDKs artifacts on the same version, even if they're declared via transitive dependencies. You can even omit versions when declaring other SDKs dependencies. I think that's the right long-term solution. Could you take a look at it when you have a chance? We can also cut a follow up ticket to track that work and merge here. What do you think?
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 with the dependency-management discussion in PR #2762 and inspect how this Android SDK currently declares and publishes Gradle or Maven artifacts. Define the BOM's scope and verify that SDK artifacts align to one version and that dependent declarations can omit individual versions. Done means the BOM is published and documented for consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100