Clean Maven Cache on Mac
Last updated: 2026-06-05
Quick answer
Maven stores artifacts at ~/.m2/repository. Old dependency versions accumulate indefinitely. Check with du -sh ~/.m2/repository. Deleting it forces re-download on next build. CodeCleaner shows Maven repo size.
Native macOS app. No account required. Local scan. You review before cleanup.
Java and Kotlin developers using Maven accumulate every dependency version ever resolved in the local repository — often several gigabytes over time.
Maven local repository
~/.m2/repository contains JARs, POMs, and metadata for all resolved artifacts. Maven never auto-prunes old versions.
Selective vs full cleanup
Remove specific groupId folders if you know they are stale, or rm -rf ~/.m2/repository for a full reset. Next mvn install re-downloads everything.
How CodeCleaner detects Maven
CodeCleaner shows ~/.m2/repository total size in its developer toolchain scan.
Manual steps (Terminal)
Run these commands in Terminal first. Scan first, review before deleting — or use CodeCleaner for a visual interface with per-item size breakdowns.
Check Maven repo size
du -sh ~/.m2/repositoryRemove local repository
rm -rf ~/.m2/repositorySafety warnings
- Full repository delete requires re-download — plan for offline builds accordingly.
Or use CodeCleaner
CodeCleaner automates this with a native macOS app. Scan first, review before deleting. Free scan, no account required.
Native macOS app. No account required. Local scan. You review before cleanup.
Frequently asked questions
- Is deleting ~/.m2/repository safe?
- Yes for regenerable artifacts. Maven re-resolves dependencies on next build.
Why developers trust CodeCleaner
- Source code is never targeted
- Only known cache and build artifact paths
- Docker cleanup through official Docker CLI
- Local-only processing — no cloud upload
- No account required
- Free scan before paying for cleanup
Native macOS app. No account required. Local scan. You review before cleanup.