Getting more out of Maven
summary
Shows concrete Maven practices: prefer mvnw verify over install to avoid polluting ~/.m2, add a Maven wrapper (used 3.9.14 in demo) for reproducible builds, run effective-pom to see exactly where values come from, and use the Maven enforcer plugin to fail builds for wrong Java/Maven versions (demo fails on Java 17, passes on Java 21). Also demos IntelliJ dependency analysis, vulnerability inspection, SDKMAN for tool management, and strategies to resolve transitive version conflicts.
AI-written summary · about
chapters (12)
- 0:00Maven optimization intro
- 2:50New Maven projects
- 4:19Maven wrapper for reproducibility
- 5:44Build with verify not install
- 13:30Maven inheritance and POM
- 19:10Maven profiles for builds
- 22:01Enforce build constraints
- 27:02Managing dependencies and plugins
- 33:29Resolving dependency conflicts
- 37:25Detecting vulnerable dependencies
- 40:21Troubleshooting Maven builds
- 41:05Summary and resources
related talks
16mMaven - Taming the Beast
43mMaven demo dump - just the useful bits
29mTools worth knowing
54mWhat I Wish I Knew About Maven Years Ago
42mApache Maven Survival Guide “Bring It On! -Mode”
46mPainless Organisation and Maintenance of Maven Builds
45mWhat's cooking in Maven?
33mBroken Buildtools and Bad Behaviors; The Maven Story