Accepted answer

settings.xml is not required (and thus not autocreated in ~/.m2 folder) unless you want to change the default settings.

standalone maven and the maven in eclipse will use the same local repository (~/.m2 folder). this means if some artifacts/dependencies are downloaded by standalone maven, it will not be again downloaded by maven in eclipse.

based on the version of eclipse that you use, you may have different maven version in eclipse compared to the standalone. it should not matter in most cases.


by installing maven you can not expect the settings.xml in your .m2 folder(if may be hidden folder, to unhide just press ctrl+h). you need to place the file explicitly at that location. after placing the file maven plugin for eclipse will start using that file too.


you can verify where your setting.xml is by pressing shortcut ctrl+3, you will see quick access on top right side of eclipse, then search setting.xml in searchbox. if you got setting.xml it will show up in search. click that, and it will open the window showing directory path wherever it is stored. your maven global settings should be as such:

global setting c:\maven\apache-maven-3.5.0\conf\settings.xml
user setting %userprofile%\\.m2\setting.xml
you can use global setting usually and leave the second option user setting untouched. store your setting.xml in global setting


i also underwent the same issue as maven doesn't create the settings.xml file under .m2 folder. what i did was the following and it works smoothly without any issues.

go to the location where you maven was unzipped.

direct to following path,

\apache-maven-3.0.4\conf\ and copy the settings.xml file and paste it inside your .m2 folder.

now create a maven project.


as per the maven's documentation, there are two possible settings.xml locations

one is the global maven's repo (your initial download and subsequent unzipped files from apache maven) $m2_home/conf/settings.xml

and the second is the user created one (your local copy) ${user.home}/.m2/settings.xml

the local copy takes precedence over the global copy in terms of settings information. but it is said that they both get merged during "runtime". if you need to have your local copy of the settings.xml, simply copy from the global copy and paste in your .m2 folder and adjust the details as needed


the settings.xml file is not created by itself, you need to manually create it. here is a sample:

  <settings xmlns=""


installation of maven doesn't create the settings.xml file. you have to create it on your own. just put it in your .m2 directory where you expected it, see for reference. the m2eclipse plugin will use the same settings file as the command line.

Related Query

More Query from same tag