Apache Maven 3.8: What's New, Release History & Support Lifecycle

Maven 3.8 Series - The "Quick Patch That Saved a Lot of Weekends" Release

Ah, Maven 3.8. Remember when 3.8.0 dropped and immediately broke the Wrapper on Windows? Yeah, the team yanked it fast and shipped 3.8.1 like a hotfix on steroids.

The 3.8 series (up to 3.8.9 before it got EOL'd) was mostly about security hardening, better CI friendliness, and fixing a bunch of annoying regressions. It introduced blocking insecure HTTP repos by default - which broke some old builds but forced everyone to clean up their act.

I ran 3.8.x for years on enterprise projects before jumping to 3.9. Solid, but man, those early Windows Wrapper issues gave me gray hairs.

The Big Fixes That Made 3.8 Usable

The team didn't mess around - they squashed the pain points fast:

• Maven Wrapper (mvnw) finally worked reliably on Windows again - no more "permission denied" nonsense
• Relative paths in settings.xml? Handled properly, no more absolute-path-only headaches
• Toolchains.xml actually got read correctly - custom JDK switching stopped failing silently
• Builds with special characters in user home (looking at you, non-ASCII usernames) stopped exploding
• ${session.executionRootDirectory} in multi-module projects? Fixed, no more weird resolution bugs
• Parallel builds (-T flag) stopped hanging randomly
• Better detection of the current project when you run Maven from deep inside subfolders

These weren't flashy features - just the kind of stuff that makes mvn clean install finish every single time instead of failing at 2 a.m. on CI.

Who Should've Upgraded (And Why Most Did)

If any of this sounds familiar, you needed 3.8 yesterday:

• You use the Maven Wrapper anywhere - especially on Windows boxes
• Relative paths in settings.xml (like pointing localRepository one folder up)
• Toolchains.xml for juggling multiple JDKs without env var hell
• Windows devs who got burned by 3.8.0 regressions
• Large multi-module builds with parallel mode turned on
• Basically anyone who wanted Maven to just work without surprises

If you were still on 3.6 or 3.7 back then, jumping straight to 3.8 gave you all the goodies (faster parallel builds, better CI properties) plus these fixes. Worth it.

How to Upgrade - Literally Takes 2 Minutes

Dead simple:

1. Grab the latest 3.8.x binary from apache.org (or just let the Wrapper do its thing)
2. Swap out your old Maven install folder
3. If you're using mvnw, just run ./mvnw -v - it pulls the right version automatically
4. Fire mvn -v and smile when it says 3.8.something

No POM changes. No settings.xml tweaks. It just works - more reliably than before.

Bottom Line - 3.8 Was the Reliable Workhorse

The 3.8 series took the shiny new stuff from the original plan (parallel build improvements, CI-friendly vars, security hardening) and polished off the rough edges fast.

It was the version most teams ran for years - stable, no drama, and the Wrapper + toolchains actually behaved.

Note: By late 2025, 3.8.x is fully EOL (no more fixes, even security). If you're somehow still on it"| upgrade to 3.9.11 already. But back in the day? 3.8 saved a lot of sanity.