When Eclipse uses MAVEN, the configuration after modifying the default central warehouse fails to find the package problem resolved

Typically when you configure MAVEN on your company's content, the Settings.xml file is configured with a client Nexus address, and if you do not specify a settings.xml file at the user directory level in eclipse, you will see a problem with the package not found.

Priority of Settings.xml:

~/.m2/settings.xml

$M 2_home/conf/settings.xml

If this file is not available in the ~/.M2 directory, it will be used by default in the $m2_home/conf directory.

So there is a phenomenon that can be performed normally at the command line, but not in eclipse.

The reason is that eclipse defaults to the existence of the ~/.m2 file, whichever is the same. Therefore, the following changes need to be made:

When Eclipse uses MAVEN, the configuration after modifying the default central warehouse fails to find the package problem resolved