Managing Dependencies for Spring Projects with Gradle
summary
Explains how Spring Boot’s Maven BOM is consumed by Gradle via the Spring Dependency Management plugin and by Gradle 5’s native platform/enforcedPlatform support, shows migration patterns (use platform vs enforcedPlatform, resolution rules, or targeted resolution strategy code), demonstrates publishing Java platforms and Gradle module metadata, and measures dependency reporting shrinking from a multi‑page plugin analysis to a single‑page native report. Notes plugin strengths: BOM property overrides and Maven‑style exclusions (exclusions still harder in native Gradle) and points out annotationProcessor scope needs explicit handling.
AI-written summary · about
chapters (12)
- 0:00Managing Spring dependencies
- 1:26Why Spring Boot needs it
- 8:28Spring’s dependency plugin
- 17:19Key plugin features
- 20:56Gradle 5 BOM support
- 23:06Gradle platform syntax
- 27:22Fine-grained rules
- 30:20Publishing BOMs
- 32:31Feature variants
- 35:26Migrating to Gradle
- 39:50Feedback and future
- 41:33Conclusion
related talks
37mMaven v Gradle: Dawn of Project Automation
20mManaging Library Versions with Gradle BOM Import
22mGradle Ex Machina
41mThe future of dependency management, seen from 2022
01h 01mDependency Management with Gradle 6.0
54mWhat I Wish I Knew About Maven Years Ago
01h 59mGradle: Give Your Build Some Love and It Will Return It!
16mMaven - Taming the Beast