zoukankan      html  css  js  c++  java
  • Maven Dependency Scopes

    Maven dependency scope attribute is used to specify the visibility of a dependency, relative to the different lifecycle phases (build, test, runtime etc). Maven provides six scopes i.e. compile, provided, runtime, test, system, and import.

    Maven dependency scope – compile

    This is maven default scope. Dependencies with compile scope are needed to build, test, and run the project.

    Scope compile is to be required in most of the cases to resolve the import statements into your java classes sourcecode.

    <dependencies>
        <dependency>
            <groupId>log4j</groupId>
            <artifactId>log4j</artifactId>
            <version>1.2.14</version>
            <!-- You can ommit this because it is default -->
            <scope>compile</scope>
        </dependency>
    </dependencies>
    

    Maven dependency scope – provided

    Maven dependency scope provided is used during build and test the project. They are also required to run, but should not exported, because the dependency will be provided by the runtime, for instance, by servlet container or application server.

    <dependency>
        <groupId>javax.servlet</groupId>
        <artifactId>servlet-api</artifactId>
        <version>3.0.1</version>
        <scope>provided</scope>
    </dependency>
    

    Maven dependency scope – runtime

    Dependencies with maven dependency scope runtime are not needed to build, but are part of the classpath to test and run the project.

    <dependency>
        <groupId>com.thoughtworks.xstream</groupId>
        <artifactId>xstream</artifactId>
        <version>1.4.4</version>
        <scope>runtime</scope>
     </dependency>
    

    Maven dependency scope – test

    Dependencies with maven dependency scope test are not needed to build and run the project. They are needed to compile and run the unit tests.

    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>test</scope>
    </dependency>
    

    Maven dependency scope – system

    Dependencies with system are similar to ones with scope provided. The only difference is system dependencies are not retrieved from remote repository. They are present under project’s subdirectory and are referred from there. See external dependency for more detail.

    <dependency>
        <groupId>extDependency</groupId>
        <artifactId>extDependency</artifactId>
        <scope>system</scope>
        <version>1.0</version>
        <systemPath>${basedir}warWEB-INFlibextDependency.jar</systemPath>
    </dependency>
    

    Maven dependency scope – import

    import scope is only supported on a dependency of type pom in the dependencyManagement section. It indicates the dependency to be replaced with the effective list of dependencies in the specified POM’s dependencyManagement section.

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>other.pom.group.id</groupId>
                <artifactId>other-pom-artifact-id</artifactId>
                <version>SNAPSHOT</version>
                <scope>import</scope>
                <type>pom</type>
            </dependency>   
        </dependencies>
    </dependencyManagement>
    

    Maven dependency transitivity resolution

    When you include a maven dependency and it has it’s own other dependencies (i.e. transitive dependencies) then you may want to be clear about the scope of these transitive dependencies as well.

    Let’s understand about maven transitive dependencies with a simple table. In this table, if a dependency is set to the scope in the left column, transitive dependencies at top row will result in a dependency with the scope listed at their intersection.

    Dependencycompileprovidedruntimetest
    compilecompileruntime
    providedprovidedprovided
    runtimeruntimeruntime
    testtesttest

    [[转载自howtodoinjava.com]]

  • 相关阅读:
    你有没有发现你的文章被人侵权?推荐一个工具给你
    带你找到五一最省的旅游路线【dijkstra算法代码实现】
    【最短路径Floyd算法详解推导过程】看完这篇,你还能不懂Floyd算法?还不会?
    Floyd算法java实现demo
    【销售系统设计01】关于线上与线下销售业绩冲突处理
    jenkins maven 自动远程发布到服务器,钉钉提醒团队
    研究windows下SVN备份及还原恢复方案
    xamarin.android SurfaceView 实现 游戏 触摸摇杆
    C++ 头文件和源文件 和 编译流程
    十大经典排序算法总结(JavaScript描述)
  • 原文地址:https://www.cnblogs.com/freesfu/p/13564300.html
Copyright © 2011-2022 走看看