Broken Buildtools and Bad Behaviors; The Maven Story
summary
Maven 3 changes the local cache semantics so artifacts are verified on use (checksums still off by default), and reactor awareness removes the need to run install to resolve multi-module dependencies; an experimental flag delays install/deploy until the entire build succeeds and claims to work for ~95% of Java projects. A clean-install extension demos a warning to stop polluting the local repo. New CI-friendly placeholders plus a build-consumer prototype rewrite POMs for reproducible CI; Maven is used by ~60–80% of Java projects yet only 5–10 active committers maintain 95 subprojects.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:32Workarounds become patterns
- 4:25Maven local repo caching
- 8:08Environment pollution in Maven
- 12:28Why Maven feels slow and how to fix it
- 17:25Myth of clean install
- 20:41Property resolution pitfalls
- 23:11Version conflicts in multi-module
- 25:43Maven Build Consumer
- 31:19POM as production code
- 32:25Contributing to Maven
related talks
16mMaven - Taming the Beast
51mMaven 4: New foundations for a classic structure
42mGetting more out of Maven
02h 27mWait no more, here comes Maven 4!
39mMaking Maven Marvellous
46mPainless Organisation and Maintenance of Maven Builds
30mReproducible Builds with Apache Maven
58mThe Current State of Apache Maven 4