文章目录
1. Maven:介绍
Maven 是什么？
Maven 是一个Apache 公司的开源项目，是一个项目构建工具。
Maven 的好处？
使用maven 可以在项目中不用导入项目依赖的jar 包，省去了下载
和导入jar 包的过程，使项目的大小等到了缩减。（统一管理依赖jar 包）
Maven 的核心？
Maven 的两大核心：依赖管理：对项目需要使用到的jar 包进行管
理；项目构建：项目在编码完成后，对项目进行编译、测试、打包、部署。
2. Maven:仓库
Maven 通过一个仓库来存放jar 包，在Maven 项目中，不再需要导入这些jar 包，只需要告诉项目所
依赖的jar 包的坐标，Maven 就会自己将我们项目所需要的jar 包给我们依赖进来。在maven 中仓库有三
种：
(1) 本地仓库：本地仓库就在自己的机器上，我们可以在自己的机器上创建一个maven 仓库，然后就
需要的jar 包导入进去，就可以在项目中引用。
(2) 私服仓库：私服仓库在公司局域网内，公司可以在自己的局域网内创建一个仓库，将项目所需要
的jar 包存放在此仓库中，这样整个项目组就都可以使用此仓库提供的jar 包，不再需要在自己本地创建仓
库来保存jar 包。
(3) 中央仓库：中央仓库是最大的一个仓库，由Apache 组织来负责维护，几乎包括了现在所有的jar
包（有一些涉及版权问题没有，比如：oracle 数据库的连接jar 包），但是中央仓库的访问速度非常慢。
Maven 如何在仓库中查找jar 包？
Maven 在仓库中查找jar 包需要使用到jar 的“坐标”信息，坐标信息由“公司名称+项目名称+版本信息”
三部分构成。（坐标：groupId、artifactId、version 三个属性就能定位一个jar 包！）
3. Maven：下载与安装配置（环境变量）
2.下载解压到D 盘或E 盘根目录即可。
以版本（apache-maven-3.5.0）为主。
3.配置环境变量：MAVEN_HOME(或M2_HOME)，其值为
D:\tools\apache-maven-3.5.0；然后PATH 环境变量最后附加上";%MAVEN_HOME%\bin"，检查方式：重新进入命令行(DOS 窗口)模式，输入mvn -version，正常情况下会显示maven 及jdk 的版本号（前提：jdk 环境必须先安装好，否则后面无法正常编译项目）。
\
4. Maven 核心配置文件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.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>F:\Xxlearning\Mavenkj\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> -->
<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>
<id>optional</id>
<active>true</active>
<protocol>http</protocol>
<username></username>
<password></password>
<host>172.16.251.58</host>
<port>3128</port>
<nonProxyHosts>localhost|127.0.0.1</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>
<id>releases</id>
<username>admin</username>
<password>Bang123</password>
</server>
<server>
<id>snapshots</id>
<username>admin</username>
<password>Bang123</password>
</server>
<!-- 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>mirrorId</id>
<mirrorOf>repositoryId</mirrorOf>
<name>Human Readable Name for this Mirror.</name>
<url>http://my.repository.com/repo/path</url>
</mirror>
<mirror>
<id>central-aliyun</id>
<mirrorOf>*</mirrorOf>
<name>aliyun-mirror</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>jdk-1.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>
<!-- 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. | -->
</settings>
\
5. 常用命令
clean：对项目进行清理，删除target目录下编译的内容
compile：编译项目源代码
test：对项目进行运行测试
package：打包文件并存放到项目的target目录下，打包好的文件通常都是编译后的class文件
install：在本地仓库生成仓库的安装包，可供其他项目引用，同时打包后的文件放到项目的target目录下
6. 在 Idea 工具中配置 Maven 工具。
1 打开 settings: 搜索关键字：maven 即可看到如下界面：
2 ：需要作如下配置：即可完成。
7.在 Idea 工具中新建 Maven 项目。
1 创建一个项目：
2 选择“Maven”后，直接点击下一步！
3 输入相关信息；
4 点击“finish”完成。
5 Maven 项目的默认目录结构：
8.Maven 构建生命周期。
9. 在 Idea 工具中新建 vmall_web 项目。
1 新建一个 maven 项目，选择web 骨架(模板)。
2 输入项目信息：
3 选择 maven 安装目录及settings.xml 文件所在路径地址；
4点击 finish 即完成。
5 加载项目时，点击 auto imported:
6 Maven-web 项目的目录结构如下：
7 Maven-web 单项目需要手动添加如下目录，并要作相应的配置！注意颜色不一样！
8 部署运行：有两种方式。第一种方式：原web 项目通过添加一个tomcat 服务
打开浏览器并输入：http://localhost:8080/即可访问
9 第二种方式：添加maven 命令的方式运行！
首先，在pom.xml 文件中配置tomcat7 插件：
_<!-- 配置 Tomcat 插件 --> _
<plugin>
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat7-maven-plugin</artifactId>
<version>2.2</version>
<configuration>
<port>8080</port>
<path>/</path>
<contextReloadable>true</contextReloadable>
</configuration>
</plugin>
执行maven 命令：把本web 项目安装到本地仓库：
添加maven 命令：
pom.xml 中的配置如下：（最终版本！）
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
<!--c3p0连接池相关-->
<dependency>
<groupId>com.mchange</groupId>
<artifactId>c3p0</artifactId>
<version>0.9.2.1</version>
</dependency>
<!--comcat框架-->
<dependency>
<groupId>commons-dbutils</groupId>
<artifactId>commons-dbutils</artifactId>
<version>1.4</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-pool2</artifactId>
<version>2.3</version>
</dependency>
<!--mysql数据库驱动的jar包-->
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.1.40</version>
</dependency>
<!--oracle数据库驱动jar包-->
<dependency>
<groupId>com.oracle</groupId>
<artifactId>ojdbc6</artifactId>
<version>11.2.0.3</version>
</dependency>
<!--jsp,servlet相关依赖-->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>jsp-api</artifactId>
<version>2.0</version>
<!--不打成包-->
<scope>provided</scope>
<exclusions>
<exclusion>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.1.0</version>
<scope>provided</scope>
</dependency>
<!--fastjson工具依赖-->
<dependency>
<groupId>com.alibaba</groupId>
<artifactId>fastjson</artifactId>
<version>1.2.49</version>
</dependency>
<!--dom4j依赖-->
<dependency>
<groupId>org.dom4j</groupId>
<artifactId>dom4j</artifactId>
<version>2.1.1</version>
</dependency>
<dependency>
<groupId>javax.servlet.jsp.jstl</groupId>
<artifactId>jstl-api</artifactId>
<version>1.2</version>
<!--排除有冲突的-->
<exclusions>
<exclusion>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
</exclusion>
<exclusion>
<groupId>javax.servlet.jsp</groupId>
<artifactId>jsp-api</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>taglibs</groupId>
<artifactId>standard</artifactId>
<version>1.1.2</version>
</dependency>
</dependencies>
各位看官》创作不易，点个赞！！！
诸君共勉：万事开头难，只愿肯放弃。
免责声明：本文章仅用于学习参考
2460
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
