Sorting and Reporting Your Dependencies with Gradle
summary
Shows how to reduce version drift by centralizing versions into a single file or a versions.toml and using Gradle 7.0 version catalogs (feature preview) or Maven boms like Firebase to avoid per-module version strings. Demonstrates diagnostic commands: --scan and dependencyInsight to see why versions resolve. Builds a client-friendly HTML report with the Ben Manes Gradle Versions Plugin plus Groovy HTML builder and Bootstrap — a working solution that took about 4–5 hours to implement.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:14Dependency basics
- 2:59Common dependency problems
- 6:14Solving versioning issues
- 10:25Centralizing dependencies
- 17:09Using version catalogs
- 22:40Reporting dependencies
- 32:14Talk summary
- 33:07Q&A session
related talks
28mEffective Gradle Scripts for Android Projects
26mGoodness, Gracious, Great Builds of Gradle
32m5 ways to improve your Android build productivity
42mWriting your own Gradle Plugin: A Deep Dive
35mThe Benevolent Gradle Overlord: Keeping Order
43mGradle in Android Studio 3.2 and beyond
43mLibrary Developer Confidential
36mMusical Chairs with Gradle: Surviving the Build Party
