Maven v Gradle: Dawn of Project Automation
summary
Live demo compares Maven and Gradle on a multi‑module Java project, showing a reproduced build break caused by conflicting transitive dependency C with two versions; Gradle shows the tree with gradlew dependencies and resolves by choosing the highest version unless overridden with resolutionStrategy.force, while Maven prefers the dependency declared closest to the root and recommends a BOM or enforced entry in the parent POM. Demo uses gradle wrapper auto‑download, mentions Maven enforcer plugin and Nebula/Takari plugins, and shows both tools can enforce rules or fail fast.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:27specify the configuration for the maven in a pom xml
- 17:48create a custom maven version with the settings
- 23:09enforce the configuration of my dependency
- 31:08impose some configuration rules on your projects
- 34:05apply plug-in
related talks
22mGradle Ex Machina
58mGradle: Harder, Better, Stronger, Faster
42mGetting more out of Maven
43mManaging Dependencies for Spring Projects with Gradle
16mMaven - Taming the Beast
54mWhat I Wish I Knew About Maven Years Ago
01h 59mGradle: Give Your Build Some Love and It Will Return It!
40mMaven Marvels: Project Generation at Warp Speed