eclipse 如何修改maven插件本地仓库jar包默认存储位置

CreateTime--2018年4月18日11:04:47

Author:Marydon

1.更改eclipse的maven本地仓库jar包保存位置

　　Eclipse-->Windows-->Preferences-->Maven-->User Settings-->

　　从网上的中心仓库下载下来的jar包，默认保存在了：C:\Users\Administrator\.m2\repository目录下，

从磁盘上打开该文件夹-->

eclipse 如何修改maven插件本地仓库jar包默认存储位置

　　-->很明显，我的下面已经下载了项目中很多正在使用的jar包-->下面需要进行迁移，分为2个步骤：

第一步：迁移

　　重新指定本地仓库位置为：D:\repository-maven，将repository文件夹直接剪切，粘贴到d盘根目录下，重命名为：repository-maven。

第二步：修改位置

　　要想修改eclipse中本地仓库默认存储位置，则必须通过修改settings.xml文件来实现（有且只有这一种方法）；

　　你会发现，settings.xml的默认存在于C:\Users\Administrator\.m2目录下，但是该目录下面并没有该文件，

　　方式一：推荐使用

　　　　搭建maven运行环境，并修改conf/settings.xml，eclipse指定该settings.xml所在路径-->剩余步骤同下。

　　方式二：

　　将下面内容进行拷贝，然后保存名称为settings.xml，

　　将该文件保存在D:\repository-maven目录下；

<?xml version="1.0" encoding="UTF-8"?>

<!--

Licensed to the Apache Software Foundation (ASF) under one

or more contributor license agreements.  See the NOTICE file

distributed with this work for additional information

regarding copyright ownership.  The ASF licenses this file

to you under the Apache License, Version 2.0 (the

"License"); you may not use this file except in compliance

with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,

software distributed under the License is distributed on an

"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

KIND, either express or implied.  See the License for the

specific language governing permissions and limitations

under the License.

-->

<!--

 | This is the configuration file for Maven. It can be specified at two levels:

 |

 |  1. User Level. This settings.xml file provides configuration for a single

 |                 user, and is normally provided in

 |                 ${user.home}/.m2/settings.xml.

 |

 |                 NOTE: This location can be overridden with the CLI option:

 |

 |                 -s /path/to/user/settings.xml

 |

 |  2. Global Level. This settings.xml file provides configuration for all

 |                 Maven users on a machine (assuming they're all using the

 |                 same Maven installation). It's normally provided in

 |                 ${maven.home}/conf/settings.xml.

 |

 |                 NOTE: This location can be overridden with the CLI option:

 |

 |                 -gs /path/to/global/settings.xml

 |

 | The sections in this sample file are intended to give you a running start

 | at getting the most out of your Maven installation. Where appropriate, the

 | default values (values used when the setting is not specified) are provided.

 |

 |-->

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"

          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

  <!-- localRepository

   | The path to the local repository maven will use to store artifacts.

   |

   | Default: ~/.m2/repository

  <localRepository>/path/to/local/repo</localRepository>

  -->

  <localRepository>C:\Users\Administrator\.m2\repository</localRepository>

  <!-- interactiveMode

   | This will determine whether maven prompts you when it needs input. If set

   | to false, maven will use a sensible default value, perhaps based on some

   | other setting, for the parameter in question.

   |

   | Default: true

  <interactiveMode>true</interactiveMode>

  -->

  <!-- offline

   | Determines whether maven should attempt to connect to the network when

   | executing a build. This will have an effect on artifact downloads,

   | artifact deployment, and others.

   |

   | Default: false

  <offline>false</offline>

  -->

  <!-- pluginGroups

   | This is a list of additional group identifiers that will be searched when

   | resolving plugins by their prefix, i.e. when invoking a command line like

   | "mvn prefix:goal". Maven will automatically add the group identifiers

   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not

   | already contained in the list.

   |-->

  <pluginGroups>

    <!-- pluginGroup

     | Specifies a further group identifier to use for plugin lookup.

    <pluginGroup>com.your.plugins</pluginGroup>

    -->

  </pluginGroups>

  <!-- proxies

   | This is a list of proxies which can be used on this machine to connect to

   | the network. Unless otherwise specified (by system property or command-

   | line switch), the first proxy specification in this list marked as active

   | will be used.

   |-->

  <proxies>

    <!-- proxy

     | Specification for one proxy, to be used in connecting to the network.

     |

    <proxy>

      <id>optional</id>

      <active>true</active>

      <protocol>http</protocol>

      <username>proxyuser</username>

      <password>proxypass</password>

      <host>proxy.host.net</host>

      <port>80</port>

      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>

    </proxy>

    -->

  </proxies>

  <!-- servers

   | This is a list of authentication profiles, keyed by the server-id used

   | within the system. Authentication profiles can be used whenever maven must

   | make a connection to a remote server.

   |-->

  <servers>

    <!-- server

     | Specifies the authentication information to use when connecting to a

     | particular server, identified by a unique name within the system

     | (referred to by the 'id' attribute below).

     |

     | NOTE: You should either specify username/password OR

     |       privateKey/passphrase, since these pairings are used together.

     |

    <server>

      <id>deploymentRepo</id>

      <username>repouser</username>

      <password>repopwd</password>

    </server>

    -->

    <!-- Another sample, using keys to authenticate.

    <server>

      <id>siteServer</id>

      <privateKey>/path/to/private/key</privateKey>

      <passphrase>optional; leave empty if not used.</passphrase>

    </server>

    -->

  </servers>

  <!-- mirrors

   | This is a list of mirrors to be used in downloading artifacts from remote

   | repositories.

   |

   | It works like this: a POM may declare a repository to use in resolving

   | certain artifacts. However, this repository may have problems with heavy

   | traffic at times, so people have mirrored it to several places.

   |

   | That repository definition will have a unique id, so we can create a

   | mirror reference for that repository, to be used as an alternate download

   | site. The mirror site will be the preferred server for that repository.

   |-->

  <mirrors>

    <!-- mirror

     | Specifies a repository mirror site to use instead of a given repository.

     | The repository that this mirror serves has an ID that matches the

     | mirrorOf element of this mirror. IDs are used for inheritance and direct

     | lookup purposes, and must be unique across the set of mirrors.

     |

    <mirror>

      <id>mirrorId</id>

      <mirrorOf>repositoryId</mirrorOf>

      <name>Human Readable Name for this Mirror.</name>

      <url>http://my.repository.com/repo/path</url>

    </mirror>

     -->

  </mirrors>

  <!-- profiles

   | This is a list of profiles which can be activated in a variety of ways,

   | and which can modify the build process. Profiles provided in the

   | settings.xml are intended to provide local machine-specific paths and

   | repository locations which allow the build to work in the local

   | environment.

   |

   | For example, if you have an integration testing plugin - like cactus -

   | that needs to know where your Tomcat instance is installed, you can

   | provide a variable here such that the variable is dereferenced during the

   | build process to configure the cactus plugin.

   |

   | As noted above, profiles can be activated in a variety of ways. One

   | way - the activeProfiles section of this document (settings.xml) - will be

   | discussed later. Another way essentially relies on the detection of a

   | system property, either matching a particular value for the property, or

   | merely testing its existence. Profiles can also be activated by JDK

   | version prefix, where a value of '1.4' might activate a profile when the

   | build is executed on a JDK version of '1.4.2_07'. Finally, the list of

   | active profiles can be specified directly from the command line.

   |

   | NOTE: For profiles defined in the settings.xml, you are restricted to

   |       specifying only artifact repositories, plugin repositories, and

   |       free-form properties to be used as configuration variables for

   |       plugins in the POM.

   |

   |-->

  <profiles>

    <!-- profile

     | Specifies a set of introductions to the build process, to be activated

     | using one or more of the mechanisms described above. For inheritance

     | purposes, and to activate profiles via <activatedProfiles/> or the

     | command line, profiles have to have an ID that is unique.

     |

     | An encouraged best practice for profile identification is to use a

     | consistent naming convention for profiles, such as 'env-dev',

     | 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. This

     | will make it more intuitive to understand what the set of introduced

     | profiles is attempting to accomplish, particularly when you only have a

     | list of profile id's for debug.

     |

     | This profile example uses the JDK version to trigger activation, and

     | provides a JDK-specific repo.

    <profile>

      <id>jdk-1.4</id>

      <activation>

        <jdk>1.4</jdk>

      </activation>

      <repositories>

        <repository>

          <id>jdk14</id>

          <name>Repository for JDK 1.4 builds</name>

          <url>http://www.myhost.com/maven/jdk14</url>

          <layout>default</layout>

          <snapshotPolicy>always</snapshotPolicy>

        </repository>

      </repositories>

    </profile>

    -->

    <!--

     | Here is another profile, activated by the system property 'target-env'

     | with a value of 'dev', which provides a specific path to the Tomcat

     | instance. To use this, your plugin configuration might hypothetically

     | look like:

     |

     | ...

     | <plugin>

     |   <groupId>org.myco.myplugins</groupId>

     |   <artifactId>myplugin</artifactId>

     |

     |   <configuration>

     |     <tomcatLocation>${tomcatPath}</tomcatLocation>

     |   </configuration>

     | </plugin>

     | ...

     |

     | NOTE: If you just wanted to inject this configuration whenever someone

     |       set 'target-env' to anything, you could just leave off the

     |       <value/> inside the activation-property.

     |

    <profile>

      <id>env-dev</id>

      <activation>

        <property>

          <name>target-env</name>

          <value>dev</value>

        </property>

      </activation>

      <properties>

        <tomcatPath>/path/to/tomcat/instance</tomcatPath>

      </properties>

    </profile>

    -->

  </profiles>

  <!-- activeProfiles

   | List of profiles that are active for all builds.

   |

  <activeProfiles>

    <activeProfile>alwaysActiveProfile</activeProfile>

    <activeProfile>anotherAlwaysActiveProfile</activeProfile>

  </activeProfiles>

  -->

</settings>

　　找到<localRepository>标签-->该标签指定了本地标签的保存位置-->将其改为：D:\repository-maven；

eclipse 如何修改maven插件本地仓库jar包默认存储位置

　　修改settings.xml文件的位置；

　　eclipse-->点击右侧的Browse..按钮-->选择settings.xml所在路径-->你会发现本地仓库位置已经发生变更-->点击"Apply"即可。

eclipse 如何修改maven插件本地仓库jar包默认存储位置

2.修改maven资源库下载地址（默认的中心仓库）

　　默认是从maven资源库的官网地址：http://mvnrepository.com 下载jar包到本地，

但是我们也可以自行修改从别的地方下载jar包，比如：阿里，http://maven.aliyun.com/nexus/content/groups/public

方法：将配置文件中指定mirror的部分由默认修改为阿里即可。

步骤：

　　打开setting.xml-->将下面代码拷贝到mirrors标签-->

<mirror>

    <id>nexus-aliyun</id>

    <mirrorOf>central</mirrorOf>

    <name>Nexus aliyun</name>

    <url>http://maven.aliyun.com/nexus/content/groups/public</url>

</mirror>

　　-->Eclipse-->Windows-->Preferences-->Maven-->User Settings-->点击"Update Settings"即可。