This quick writeup will focus on where Maven stores all the local dependencies locally – which is in the Maven local repository.
Simply put, when we run a Maven build, all the dependencies of our project (jars, plugin jars, other artifacts) are all stored locally for later use.
Also keep in mind that, beyond just this type of local repository, Maven does support 3 types of repos:
- Local – Folder location on the local Dev machine
- Central – Repository provided by Maven community
- Remote – Organization owned custom repository
Let’s now focus on the local repository.
2. The Local Repository
The local repository of Maven is a folder location on the developer’s machine, where all the project artifacts are stored locally.
When maven build is executed, Maven automatically downloads all the dependency jars into the local repository.
Usually this folder is named .m2.
Here’s where the default path to this folder is – based on OS:
And of course, for both on Linux or Mac:
3. No Repository in the Default Location
If the repo is not present in this default location, it’s likely because some pre-existing configuration.
That config file is located in the Maven installation directory – in a folder called conf – and is named settings.xml.
Here’s the relevant configuration that determines the location of our missing local repo:
<settings> <localRepository>C:/maven_repository</localRepository> ...
That’s essentially how we can change the location of the local repo – and of course, if that location is changed, we’ll no longer find the repo at the default location.
Note: The files stored in the earlier location will not be moved automatically.
In this quick tutorial we had a look on the Maven local repository default setup and the custom configuration on it to change the repo location.