The future of dependency management, seen from 2022
summary
Dependency upgrades are tedious and error prone; the talk claims Gradle’s version catalogs and the MIT-licensed Gradle plugin refreshVersions cut that friction by centralizing versions in a versions.properties file, offering IDE autocomplete for AndroidX/Kotlin, running a gradle task locally, and resolving metadata in parallel (one example shrinks a 100-dependency lookup from ~5 minutes to ~5 seconds). It demos migration to version catalogs, Kotlin Multiplatform support, avoids build-invalidations, and flags transitive/compatibility risks like API breakage and unexpected upgrades.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 2:17Common dependency problems
- 6:37Current dependency upgrade solutions
- 13:38Demo of RefreshVersions
- 20:02Benefits of RefreshVersions
- 25:36Risks of third-party dependencies
- 30:52Solutions for dependency risks
- 32:16Challenges in dependency management
- 33:41Future of dependency discovery
- 37:52Metadata and reliability needs
- 39:17Credits and acknowledgments
related talks
36mThe future of dependency management, seen from 2022
42mDependency Updates: Before and After
01h 01mDependency Management with Gradle 6.0
25mMigrate to Gradle version catalog and convention plugins
38mKnow thy neighbours: dependency management done right.
23mMetadawhat? Managing compatibility of your Kotlin apps and libraries
02h 49mGradle: Give Your Build Some Love and It Will Love You Back!
01h 59mGradle: Give Your Build Some Love and It Will Return It!