Managing Library Versions with Gradle BOM Import

on YouTube ↗20m

" summary

Android Studio 3.4+ with Gradle 4.6+ can import Maven BOMs so a single platform file supplies group:artifact version mappings; Gradle 5.0 adds version alignment and Kotlin DSL/platform APIs. Examples shown include using OkHttp/Square BOMs via implementation(platform("com.squareup.okhttp3:okhttp-bom:VERSION")) and the DroidKaigi app centralizing libraries this way; module-level explicit versions still take precedence unless force=true or an enforcedPlatform is used. The talk notes large server BOMs exist (e.g., GCP ~154 artifacts, AWS ~167) for covering many dependencies.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 1:49Gradle dependency management
3. 6:41BOM basics
4. 12:18BOM in Gradle 5.0
5. 17:48Future outlook

" related talks

• 43mManaging Dependencies for Spring Projects with GradleAndy Wilkinson, Jennifer Strater · Spring I/O 2019
• 47mThe definitive guide to Android library developmentJeroen Mols · Android Makers 2022
• 39mThe definitive guide to Android library developmentJeroen Mols · droidcon Berlin 2021
• 01h 01mDependency Management with Gradle 6.0René Gröschke · SnowOne 2020
• 31mGradle in Android Studio 3.2 and beyondAlex Ruiz · Droidcon Italy 2018
• 44mBuilding and Publishing Android Libraries the Missing GuideMilos Marinkovic · GDG DevFest Gorky 2018
• 43mLibrary Developer ConfidentialElliott Chenger · 360|AnDev 2018
• 41mThe future of dependency management, seen from 2022Louis CAD · droidcon New York 2022