Expand Authors Top

If you have a few years of experience in the Java ecosystem and you’d like to share that with the community, have a look at our Contribution Guidelines.

November Discount Launch 2022 – Top
We’re finally running a Black Friday launch. All Courses are 30% off until next Friday:


November Discount Launch 2022 – TEMP TOP (NPI)
We’re finally running a Black Friday launch. All Courses are 30% off until next Friday:


Expanded Audience – Frontegg – Security (partner)
announcement - icon User management is very complex, when implemented properly. No surprise here.

Not having to roll all of that out manually, but instead integrating a mature, fully-fledged solution - yeah, that makes a lot of sense.
That's basically what Frontegg is - User Management for your application. It's focused on making your app scalable, secure and enjoyable for your users.
From signup to authentication, it supports simple scenarios all the way to complex and custom application logic.

Have a look:

>> Elegant User Management, Tailor-made for B2B SaaS

1. Overview

In this short tutorial, we'll explore ways to clear our local Maven cache. We may want to do this in order to save disk space or clear up artifacts that we no longer reference.

We'll first clear the cache manually, where we physically delete the directory. Then, we'll clear our cache using the Maven Dependency Plugin, using some of the different plugin options available to us.

2. Deleting the Local Cache Directory

Our local Maven repositories are stored in different locations based on the operating system. Also, as the .m2 directory is likely to be hidden, we'll need to change the directory properties in order to display it.

In Windows, the default location is:


And on the Mac:


And on Linux-based systems:


Once we locate the directory, we can simply delete the folder .m2/repository. With Unix-based systems like MacOS or Linux, we can delete the directory with one command:

rm -rf ~/.m2/repository

If our cache directory isn't in the default location, we can use the Maven Help Plugin to locate it:

mvn help:evaluate -Dexpression=settings.localRepository -q -DforceStdout

3. Using the Maven Dependency Plugin

Instead of deleting the cache directory directly, we can use the Maven Dependency Plugin with the purge-local-repository goal.

First, we need to navigate to the root of our Maven project. Then, we can run:

mvn dependency:purge-local-repository

When we run this plugin without any additional flags, it may download artifacts that aren't present in our cache to resolve the dependency tree. This is known as transitive dependency resolution. Next, it deletes our local cache and, finally, re-downloads the artifacts.

Alternatively, in order to delete our cache and avoid the first step of pre-downloading the missing dependencies, we can pass in the flag actTransitively=false:

mvn dependency:purge-local-repository -DactTransitively=false

Finally, if we just want to clear out our cache, without pre-downloading or re-resolving the artifacts:

mvn dependency:purge-local-repository -DactTransitively=false -DreResolve=false

Here, we pass in an additional flag of reResolve=false, which tells the plugin to avoid re-downloading the dependencies.

4. Conclusion

In this short article, we looked at two ways to clear our local Maven cache.

First, we looked at manually emptying our local cache directory. Then, we used the Maven Dependency Plugin, exploring different options to achieve our desired outcome.

November Discount Launch 2022 – Bottom
We’re finally running a Black Friday launch. All Courses are 30% off until next Friday:


Maven footer banner
Inline Feedbacks
View all comments
Comments are closed on this article!