Dependency management? Model it!
summary
Explains concrete Gradle techniques: publish rich Gradle module metadata and use platform alignment (BOM import plus module metadata loops) to keep multi-jar frameworks in sync; declare dependency constraints and the strictly enforced version (double-bang) to downgrade and publish mandatory versions; run the dependency analysis plugin and build scans to see selection reasons and unused dependencies; resolve runtime implementation conflicts with capability resolution (choose log4j2 or substitute artifacts) and use substitution or reject rules for Jakarta/Javax migration.
AI-written summary · about
chapters (7)
- 0:00Introduction to Gradle
- 4:10Declaring dependencies
- 7:38Constraints and platforms
- 14:26Managing version conflicts
- 22:29Dependency alignment
- 31:08Implementation conflicts
- 45:37Q&A and conclusion
related talks
48mPicking a Winner: How to Pick the Right Dependency (Resolution...
20mOSS Dependency Health: Towards Maturity and Sustainability Risk Assessment Model
36mSBOMs, VEX, and Kubernetes
44mDatabase Change Management
58mMaintain Social Distance this Spring
58mHow Can Package Managers Handle ABI (In)compatibility in C++?
39mUsing GraphDB Technology to Resolve Transitive Vulnerabilities at Scale
24mBuilding a Better Database: How GitHub Structures Their Advisory Database to Drive Developer ...