And Gradle says: sharing is caring - Or why Gradle Plugins are all you need for your Configuration
summary
Gradle plus Kotlin DSL uses version catalog TOML files to centralize versions, libraries, plugins and bundles, letting teams publish catalogs to Maven/GitHub/Artifactory and sign for Maven Central. Plugins encapsulate configuration and extensions, support programmatic overrides (versions, libraries, bundles), and composite builds let consumers test changes locally without publishing. A settings plugin can inject catalogs across repos so bumping a single version string updates many projects and removes repeated boilerplate.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:33Problems with Gradle setup
- 2:38Evolution of dependency management
- 8:57Version catalogs explained
- 13:31Publishing version catalogs
- 15:59Overriding versions in catalogs
- 17:23Abusing version catalogs for non-JVM
- 19:33Testing dependencies locally
- 20:57Reducing build file boilerplate
- 21:39Creating Gradle plugins
- 24:50Distributing plugins and meta-plugins
- 26:16Using plugins in local projects
- 26:57Settings plugins for version catalogs
- 28:44Summary and Q&A setup
related talks
49mGradle Ex Machina
25mMigrate to Gradle version catalog and convention plugins
33mUnderstanding Gradle and writing your own Gradle Plugin
02h 49mGradle: Give Your Build Some Love and It Will Love You Back!
38mGradle Without The Guesswork: A Guide for Kotlin Developers
41mThe future of dependency management, seen from 2022
21mMake Gradle work for you, create your own tasks and plugins
35mHow to write Gradle plugins (in Kotlin)