Apps
Maven Cache
Maven stores downloaded artifacts in the local repository under .m2/repository so builds can reuse JARs, POMs, plugin distributions, metadata XML, checksum files, and partially downloaded transfer markers instead of fetching them every time. Over time that cache can accumulate outdated snapshots, corrupted archives, failed-download leftovers, and duplicate versions from many projects. Kudu removes these cached repository files so Maven can redownload clean copies without touching your source code, project settings, accounts, or credentials.
Why clean Maven Cache?
- A truncated JAR or POM left behind after a dropped connection causes build failures like zip END header errors, invalid LOC header messages, or non-parseable POM warnings
- Stale SNAPSHOT artifacts in the local repository make Maven compile against old code, so recent fixes seem to be ignored until the dependency is forced to update
- Corrupted maven-metadata.xml or checksum files lead to checksum mismatch and could not resolve artifact errors even though the dependency exists remotely
- Leftover .lastUpdated transfer markers from a temporary repository outage can block retries, causing repeated resolution failures on every build
- Plugin artifacts cached from an interrupted download can break goals such as test, package, or deploy, with errors that point to missing classes inside Maven plugins
- Large multi-project workspaces accumulate many unused versions of the same dependencies, and developers notice .m2 consuming tens of gigabytes and slowing backup, indexing, and disk scans
- Repeated downloads and overwrites of repository files can fragment the local store on disk, and cleaning lets Maven rebuild only what is needed while leaving your projects and settings untouched
What gets cleaned
Cache paths Kudu targets
Windows
~/.m2/repository |
macOS
~/.m2/repository |
Linux
~/.m2/repository |
Frequently asked
Common questions about Maven Cache
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.