- <</SPAN>project>
-
... -
<</SPAN>dependencies> -
<</SPAN>dependency> -
<</SPAN>groupId>group-a</</SPAN>groupId> -
<</SPAN>artifactId>artifact-a</</SPAN>artifactId> -
<</SPAN>version>1.0</</SPAN>version> -
<</SPAN>exclusions> -
<</SPAN>exclusion> -
<</SPAN>groupId>group-c</</SPAN>groupId> -
<</SPAN>artifactId>excluded-artifact</</SPAN>artifactId> -
</</SPAN>exclusion> -
</</SPAN>exclusions> -
</</SPAN>dependency> -
<</SPAN>dependency> -
<</SPAN>groupId>group-a</</SPAN>groupId> -
<</SPAN>artifactId>artifact-b</</SPAN>artifactId> -
<</SPAN>version>1.0</</SPAN>version> -
<</SPAN>type>bar</</SPAN>type> -
<</SPAN>scope>runtime</</SPAN>scope> -
</</SPAN>dependency> -
</</SPAN>dependencies> - </</SPAN>project>
- <</SPAN>dependencies>
-
<</SPAN>dependency> -
<</SPAN>groupId>junit</</SPAN>groupId> -
<</SPAN>artifactId>junit</</SPAN>artifactId> -
<</SPAN>version>3.8.1</</SPAN>version> -
<</SPAN>scope>test</</SPAN>scope> -
</</SPAN>dependency> -
</</SPAN>dependencies>
2. 依赖范围
compile: 编译依赖范围。如果没有指定,就会默认使用该依赖范围。使用此依赖范围的Maven依赖,对于编译、测试、运行三种classpath都有效。
test: 测试依赖范围。使用此依赖范围的Maven依赖,只对于测试classpath有效,在编译主代码或者运行项目的使用时将无法使用此类依赖。典型的例子就是JUnit,它只有在编译测试代码及运行测试的时候才需要。
provided: 已提供依赖范围。使用此依赖范围的Maven依赖,对于编译和测试classpath有效,但在运行时无效。典型的例子是servlet-api,编译和测试项目的时候需要该依赖,但在运行项目的时候,由于容器已经提供,就不需要Maven重复地引入一遍。
runtime: 运行时依赖范围。使用此依赖范围的Maven依赖,对于测试和运行classpath有效,但在编译主代码时无效。典型的例子是JDBC驱动实现,项目主代码的编译只需要JDK提供的JDBC接口,只有在执行测试或者运行项目的时候才需要实现上述接口的具体JDBC驱动。
system: 系统依赖范围。该依赖与三种classpath的关系,和provided依赖范围完全一致。但是,使用system范围依赖时必须通过systemPath元素显式地指定依赖文件的路径。由于此类依赖不是通过Maven仓库解析的,而且往往与本机系统绑定,可能造成构建的不可移植,因此应该谨慎使用。systemPath元素可以引用环境变量,如:
- <</SPAN>dependency>
-
<</SPAN>groupId>javax.sql</</SPAN>groupId> -
<</SPAN>artifactId>jdbc-stdext</</SPAN>artifactId> -
<</SPAN>version>2.0</</SPAN>version> -
<</SPAN>scope></</SPAN>scope> -
<</SPAN>systemPath>${java.home}/lib/rt.jar</</SPAN>systemPath> - </</SPAN>dependency>
import(Maven 2.0.9及以上): 导入依赖范围。该依赖范围不会对三种classpath产生实际的影响,稍后会介绍到。
3. 传递性依赖
POM.xml配置如下:
- <</SPAN>project
xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" -
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> -
<</SPAN>modelVersion>4.0.0</</SPAN>modelVersion> -
-
<</SPAN>groupId>com.mycompany.app</</SPAN>groupId> -
<</SPAN>artifactId>my-app-simple</</SPAN>artifactId> -
<</SPAN>version>0.0.1-SNAPSHOT</</SPAN>version> -
<</SPAN>packaging>jar</</SPAN>packaging> -
-
<</SPAN>name>my-app-simple</</SPAN>name> -
<</SPAN>url>http://maven.apache.org</</SPAN>url> -
-
<</SPAN>properties> -
<</SPAN>project.build.sourceEncoding>UTF-8</</SPAN>project.build.sourceEncoding> -
</</SPAN>properties> -
-
<</SPAN>dependencies> -
<</SPAN>dependency> -
<</SPAN>groupId>junit</</SPAN>groupId> -
<</SPAN>artifactId>junit</</SPAN>artifactId> -
<</SPAN>version>3.8.1</</SPAN>version> -
<</SPAN>scope>test</</SPAN>scope> -
</</SPAN>dependency> -
-
<</SPAN>dependency> -
<</SPAN>groupId>org.springframework</</SPAN>groupId> -
<</SPAN>artifactId>spring-core</</SPAN>artifactId> -
<</SPAN>version>2.5.6</</SPAN>version> -
</</SPAN>dependency> -
</</SPAN>dependencies> - </</SPAN>project>
点击POM我们会看到该文件包含了一个commons-logging依赖:
- <</SPAN>dependency>
-
<</SPAN>groupId>commons-logging</</SPAN>groupId> -
<</SPAN>artifactId>commons-logging</</SPAN>artifactId> -
<</SPAN>version>1.1.1</</SPAN>version> - </</SPAN>dependency>
4. 可选依赖
- <</SPAN>dependency>
-
<</SPAN>groupId>commons-logging</</SPAN>groupId> -
<</SPAN>artifactId>commons-logging</</SPAN>artifactId> -
<</SPAN>version>1.1.1</</SPAN>version> -
<</SPAN>optional>true<</SPAN>optional> - </</SPAN>dependency>
那么依赖该项目的另以项目将不会得到此依赖的传递
比如上例中的项目,我们不想引入传递性依赖commons-logging,我们可以使用exclusions元素声明排除依赖,exclusions可以包含一个或者多个exclusion子元素,因此可以排除一个或者多个传递性依赖。需要注意的是,声明exclusions的时候只需要groupId和artifactId,而不需要version元素,这是因为只需要groupId和artifactId就能唯一定位依赖图中的某个依赖。换句话说,Maven解析后的依赖中,不可能出现groupId和artifactId相同,但是version不同的两个依赖。
- <</SPAN>dependency>
-
<</SPAN>groupId>org.springframework</</SPAN>groupId> -
<</SPAN>artifactId>spring-core</</SPAN>artifactId> -
<</SPAN>version>2.5.6</</SPAN>version> -
<</SPAN>exclusions> -
<</SPAN>exclusion> -
<</SPAN>groupId>commons-logging</</SPAN>groupId> -
<</SPAN>artifactId>commons-logging</</SPAN>artifactId> -
</</SPAN>exclusion> -
</</SPAN>exclusions> - </</SPAN>dependency>
- <</SPAN>project
xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" -
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> -
<</SPAN>modelVersion>4.0.0</</SPAN>modelVersion> -
-
<</SPAN>groupId>com.mycompany.app</</SPAN>groupId> -
<</SPAN>artifactId>my-app-simple</</SPAN>artifactId> -
<</SPAN>version>0.0.1-SNAPSHOT</</SPAN>version> -
<</SPAN>packaging>jar</</SPAN>packaging> -
<</SPAN>name>my-app-simple</</SPAN>name> -
<</SPAN>properties> -
<</SPAN>springframework.version>2.5.6</</SPAN>springframework.version> -
</</SPAN>properties> -
-
<</SPAN>dependencies> -
<</SPAN>dependency> -
<</SPAN>groupId>junit</</SPAN>groupId> -
<</SPAN>artifactId>junit</</SPAN>artifactId> -
<</SPAN>version>3.8.1</</SPAN>version> -
<</SPAN>scope>test</</SPAN>scope> -
</</SPAN>dependency> -
-
<</SPAN>dependency> -
<</SPAN>groupId>org.springframework</</SPAN>groupId> -
<</SPAN>artifactId>spring-core</</SPAN>artifactId> -
<</SPAN>version>${springframework.version}</</SPAN>version> -
</</SPAN>dependency> -
<</SPAN>dependency> -
<</SPAN>groupId>org.springframework</</SPAN>groupId> -
<</SPAN>artifactId>spring-beans</</SPAN>artifactId> -
<</SPAN>version>${springframework.version}</</SPAN>version> -
</</SPAN>dependency> -
</</SPAN>dependencies> - </</SPAN>project>
6. 在Eclipse中管理依赖
安装好m2eclipse之后(第2课有详细讲解)就可以用eclipse来管理依赖。
如图,在该项目的pom.xml中点击Dependency Hierarchy可以看到依赖树:
如下图,搜素org.springframework(此处是从Maven中心仓库进行搜索),选择你想要的模块和版本,点击OK即可: