- 一. 安裝與配置
- 1.1官網下載安裝包
- 1.1、官網下載安裝包
- 1.2、配置環境變量
- 1.3、本地倉儲配置
- 1.4、中央倉庫配置
- 二.eclipse中使用maven
- 2.1 eclipse配置maven
- 2.2 在eclipse中 使用maven創建項目
一 . 安裝與配置
其實主流的開發工具如IDEA、Eclipse都集成了Maven（可見重要性），但爲了更加深刻的學習與管理該工具（比如多個IDE共享的問題），個人建議還是單獨安裝比較好。
1.1、官網下載安裝包
在瀏覽器中打開下載地址：http://maven.apache.org/download.cgi
1.2、配置環境變量
注意：安裝maven之前，必須先確保你的機器中已經安裝了JDK，如果是Maven3則必須JDK1.7以上。
1．下載後解壓壓縮包，本人解壓到，D:\maven\apache-maven-3.6.1目錄下，注意：安裝路徑下沒有中文
2．添加環境變量MAVEN_HOME，值爲apache-maven的安裝路徑(沒有中文)
3．在Path環境變量的變量值末尾添加%MAVEN_HOME%\bin;
window7 系統要用";"間隔，如下圖，win10，直接添加即可
4．在命令行中輸入mvn –version，如果出現maven的版本信息，說明配置成功。
1.3、本地倉儲配置
如果您不配置，默認會在如下位置存放從遠程下載到的包：
從中央倉庫下載的jar包，都會統一存放到本地倉庫中。我們需要配置本地倉庫的位置。
打開maven安裝目錄，打開conf目錄下的setting.xml文件。
可以參照下圖配置本地倉儲位置。
你還可以在運行時指定本地倉庫位置：
mvn clean install -Dmaven.repo.local=d:\yourpath
1.4、中央倉庫配置
當構建一個Maven項目時，首先檢查pom.xml文件以確定依賴包的下載位置，執行順序如下：
1、從本地資源庫中查找並獲得依賴包，如果沒有，執行第2步。
2、從Maven默認中央倉庫中查找並獲得依賴包如果沒有，執行第3步。
3、如果在pom.xml中定義了自定義的遠程倉庫，那麼也會在這裏的倉庫中進行查找並獲得依賴包，如果都沒有找到，那麼Maven就會拋出異常。
修改默認中央倉庫地址
<mirror>
<id>nexus-aliyun</id>
<mirrorOf>*,!jeecg,!jeecg-snapshots</mirrorOf>
<name>Nexus aliyun</name>
<url>http://maven.aliyun.com/nexus/content/groups/public</url>
</mirror>
</mirrors>
以下爲常用地址，建議使用阿里雲
1、http://www.sonatype.org/nexus/ 私服nexus工具使用
2、http://mvnrepository.com/ （推薦）
3、http://repo1.maven.org/maven2
4、http://maven.aliyun.com/nexus/content/groups/public/ 阿里雲 （強力推薦）
5、http://repo2.maven.org/maven2/ 私服nexus工具使用
6、http://uk.maven.org/maven2/
7、http://repository.jboss.org/nexus/content/groups/public
8、http://maven.oschina.net/content/groups/public/
9、http://mirrors.ibiblio.org/maven2/
10、http://maven.antelink.com/content/repositories/central/
11、http://nexus.openkoala.org/nexus/content/groups/Koala-release/
12、http://maven.tmatesoft.com/content/groups/public/
提供本人配置完整的settings.xml
<?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.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: ${user.home}/.m2/repository
<localRepository>/path/to/local/repo</localRepository>
-->
<localRepository>D:\maven\InstallFiles\javaKit\mavenRes</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>
-->
<mirror>
<id>nexus-aliyun</id>
<mirrorOf>*,!jeecg,!jeecg-snapshots</mirrorOf>
<name>Nexus aliyun</name>
<url>http://maven.aliyun.com/nexus/content/groups/public</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>
-->
<profile>
<id>jdk1.8</id>
<activation>
<activeByDefault>true</activeByDefault>
<jdk>1.8</jdk>
</activation>
<properties>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<maven.compiler.compilerVersion>1.8</maven.compiler.compilerVersion>
</properties>
</profile>
</profiles>
<!-- activeProfiles
| List of profiles that are active for all builds.
|
<activeProfiles>
<activeProfile>alwaysActiveProfile</activeProfile>
<activeProfile>anotherAlwaysActiveProfile</activeProfile>
</activeProfiles>
-->
</settings>
二 . maven在eclipse中的使用
2.1 配置maven
eclipse一個集成的開發環境，在開發過程中用的很廣泛，下面看如何在eclipse中使用maven，在eclipse的4.4以上的版本加入了對maven的支持，即不需要安裝maven插件，但對4.4以下的版本需要自己安裝插件，可以在下面的網址：http://marketplace.eclipse.org/content/maven-integration-eclipse-luna，去了解安裝過程，安裝完成之後，
1、在windows–>>preferences中找到maven選項，下圖，
上圖中我們找到maven–>>installations看到，已經有了，但是我們要使用剛纔安裝的maven，選擇add按鈕，找到剛纔解壓的maven的路徑，如下，
2、eclipse中更新配置文件：
在eclipse中windows–>preferences，找到maven，然後如下圖所示，找到User settings，修改配置文件爲剛纔修改的配置文件，
全局配置（global settings ）
本臺電腦的配置，使用這臺電腦的所有用戶都是用這個配置
個人配置（user settings）
當前用戶的配置
個人配置（user settings ）會覆蓋全局配置（global settings）
修改完成之後，則和eclipse的集成完成。
經過以上的步驟則maven和eclipse的集成完成，接下來可以使用maven了，但，如果你的電腦是通過代理上網的話，必須在settings.xml文件中配置代理，這樣纔可以從maven的倉庫中下載所需的文件，配置的代理的方式如下，在settings.xml文件中添加如下內容，
<proxy>
<id>myProxy</id>
<active>true</active>
<protocol>http</protocol>
<username></username>
<password></password>
<host>proxy.xxxxx</host>
<port>910</port>
</proxy>
<!--
id 代理ID 標識代理
active 設置代理是否啓用
protocol 代理使用的協議
username 連接代理的用戶名，如，此代理不需要用戶名則可以把此標籤刪掉
password 連接代理的密碼，如，同上
host 代理的網址
port 代理使用的端口
上面是使用代理上網的配置，如果上網沒使用代理，則不需要配置。
-->
2.2 在eclipse中 使用maven創建項目
java開發過程中使用的最多的是java、javaWeb項目，
file–>>new—>project，然後找到maven，如下圖選擇，
點擊next
選擇webapp，點擊next
第一個紅框內表示的是新建java項目，第二個是javaWeb項目，這裏選擇第一個，
輸入紅框的內容之後，點擊finish，ecplise則會開始創建項目，此時會連接網絡從網上下載需要的jar包，jar包存放的路徑就是配置的本地倉庫的路徑，我的在：D:\maven\InstallFiles\javaKit\mavenResy路徑下，在D:\maven\InstallFiles\javaKit\mavenRes\org\apache\maven\plugins文件夾下是maven插件所需的依賴插件。