Gradle依赖项学习总结,dependencies、transitive、force、exclude的使用与依赖冲突解决
http://www.paincker.com/gradle-dependencies
https://docs.gradle.org/current/userguide/dependency_management.html
http://www.concretepage.com/build-tools/gradle/gradle-exclude-transitive-dependency-example
Gradle是一个非常好用的编译工具,特别是继承了maven的依赖项管理功能,需要的Library不需要像传统IDE一样手动下载复制到项目中,只需要简单的写一行gradle脚本,就能自动下载下来并编译。
但是有时候会出现各种不明情况的报错,最常见的一种原因就是依赖项版本冲突。
每个模块都可能依赖其他模块,这些模块又会依赖别的模块。而一个项目中的多个模块,对同一个模块的不同版本有依赖,就可能产生冲突。
通过gradle命令查看依赖树,可以比较直观的看到冲突。具体方法是在模块所在的目录,也即build.gradle所在目录下执行gradle dependencies(需要将gradle加入PATH环境变量),执行结果如图。

Transitive
Transitive用于自动处理子依赖项。默认为true,gradle自动添加子依赖项,形成一个多层树形结构;设置为false,则需要手动添加每个依赖项。
案例
以安卓单元测试espresso的配置为例,gradle依赖如下:
dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
运行gradle dependencies的结果如下。可以看到每个包的依赖项都被递归分析并添加进来。
+--- com.android.support.test:runner:0.2| +--- junit:junit-dep:4.10| | \--- org.hamcrest:hamcrest-core:1.1| +--- com.android.support.test:exposed-instrumentation-api-publish:0.2| \--- com.android.support:support-annotations:22.0.0+--- com.android.support.test:rules:0.2| \--- com.android.support.test:runner:0.2 (*)\--- com.android.support.test.espresso:espresso-core:2.1+--- com.android.support.test:rules:0.2 (*)+--- com.squareup:javawriter:2.1.1+--- org.hamcrest:hamcrest-integration:1.1| \--- org.hamcrest:hamcrest-core:1.1+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- org.hamcrest:hamcrest-library:1.1| \--- org.hamcrest:hamcrest-core:1.1+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- com.android.support.test:runner:0.2 (*)+--- javax.annotation:javax.annotation-api:1.2\--- org.hamcrest:hamcrest-core:1.1
统一指定transitive
可以给dependencies统一指定transitive为false,再次执行dependencies可以看到如下结果。
configurations.all {transitive = false}dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
+--- com.android.support.test:runner:0.2+--- com.android.support.test:rules:0.2\--- com.android.support.test.espresso:espresso-core:2.1
单独指定依赖项的transitive
dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1') {transitive = false}}
版本冲突
在同一个配置下(例如androidTestCompile),某个模块的不同版本同时被依赖时,默认使用最新版,gradle同步时不会报错。例如下面的hamcrest-core和runner。
dependencies {androidTestCompile('com.android.support.test:runner:0.4')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
+--- com.android.support.test:runner:0.4| +--- com.android.support:support-annotations:23.0.1| +--- junit:junit:4.12| | \--- org.hamcrest:hamcrest-core:1.3| \--- com.android.support.test:exposed-instrumentation-api-publish:0.4+--- com.android.support.test:rules:0.2| \--- com.android.support.test:runner:0.2 -> 0.4 (*)\--- com.android.support.test.espresso:espresso-core:2.1+--- com.android.support.test:rules:0.2 (*)+--- com.squareup:javawriter:2.1.1+--- org.hamcrest:hamcrest-integration:1.1| \--- org.hamcrest:hamcrest-core:1.1 -> 1.3+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- org.hamcrest:hamcrest-library:1.1| \--- org.hamcrest:hamcrest-core:1.1 -> 1.3+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- com.android.support.test:runner:0.2 -> 0.4 (*)+--- javax.annotation:javax.annotation-api:1.2\--- org.hamcrest:hamcrest-core:1.1 -> 1.3
Force
force强制设置某个模块的版本。
configurations.all {resolutionStrategy {force 'org.hamcrest:hamcrest-core:1.3'}}dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
可以看到,原本对hamcrest-core 1.1的依赖,全部变成了1.3。
+--- com.android.support.test:runner:0.2| +--- junit:junit-dep:4.10| | \--- org.hamcrest:hamcrest-core:1.1 -> 1.3| +--- com.android.support.test:exposed-instrumentation-api-publish:0.2| \--- com.android.support:support-annotations:22.0.0+--- com.android.support.test:rules:0.2| \--- com.android.support.test:runner:0.2 (*)\--- com.android.support.test.espresso:espresso-core:2.1+--- com.android.support.test:rules:0.2 (*)+--- com.squareup:javawriter:2.1.1+--- org.hamcrest:hamcrest-integration:1.1| \--- org.hamcrest:hamcrest-core:1.1 -> 1.3+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- org.hamcrest:hamcrest-library:1.1| \--- org.hamcrest:hamcrest-core:1.1 -> 1.3+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- com.android.support.test:runner:0.2 (*)+--- javax.annotation:javax.annotation-api:1.2\--- org.hamcrest:hamcrest-core:1.1 -> 1.3
Exclude
Exclude可以设置不编译指定的模块
configurations {all*.exclude group: 'org.hamcrest', module: 'hamcrest-core'}dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
+--- com.android.support.test:runner:0.2| +--- junit:junit-dep:4.10| +--- com.android.support.test:exposed-instrumentation-api-publish:0.2| \--- com.android.support:support-annotations:22.0.0+--- com.android.support.test:rules:0.2| \--- com.android.support.test:runner:0.2 (*)\--- com.android.support.test.espresso:espresso-core:2.1+--- com.android.support.test:rules:0.2 (*)+--- com.squareup:javawriter:2.1.1+--- org.hamcrest:hamcrest-integration:1.1+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- org.hamcrest:hamcrest-library:1.1+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- com.android.support.test:runner:0.2 (*)\--- javax.annotation:javax.annotation-api:1.2
单独使用group或module参数
exclude后的参数有group和module,可以分别单独使用,会排除所有匹配项。例如下面的脚本匹配了所有的group为’com.android.support.test’的模块。
configurations {all*.exclude group: 'com.android.support.test'}dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
\--- com.android.support.test.espresso:espresso-core:2.1+--- com.squareup:javawriter:2.1.1+--- org.hamcrest:hamcrest-integration:1.1| \--- org.hamcrest:hamcrest-core:1.1+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- org.hamcrest:hamcrest-library:1.1| \--- org.hamcrest:hamcrest-core:1.1+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- javax.annotation:javax.annotation-api:1.2\--- org.hamcrest:hamcrest-core:1.1
单独给某个模块指定exclude
dependencies {androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1') {exclude group: 'org.hamcrest'}}
+--- com.android.support.test:runner:0.2| +--- junit:junit-dep:4.10| | \--- org.hamcrest:hamcrest-core:1.1| +--- com.android.support.test:exposed-instrumentation-api-publish:0.2| \--- com.android.support:support-annotations:22.0.0+--- com.android.support.test:rules:0.2| \--- com.android.support.test:runner:0.2 (*)\--- com.android.support.test.espresso:espresso-core:2.1+--- com.android.support.test:rules:0.2 (*)+--- com.squareup:javawriter:2.1.1+--- com.android.support.test.espresso:espresso-idling-resource:2.1+--- javax.inject:javax.inject:1+--- com.google.code.findbugs:jsr305:2.0.1+--- com.android.support.test:runner:0.2 (*)\--- javax.annotation:javax.annotation-api:1.2
不同配置下的版本冲突
同样的配置下的版本冲突,会自动使用最新版;而不同配置下的版本冲突,gradle同步时会直接报错。可使用exclude、force解决冲突。
例如compile 'com.android.support:appcompat-v7:23.1.1',和androidTestCompile 'com.android.support.test.espresso:espresso-core:2.1',所依赖的com.android.support:support-annotations版本不同,就会导致冲突。
dependencies {compile 'com.android.support:appcompat-v7:23.1.1'androidTestCompile('com.android.support.test:runner:0.2')androidTestCompile('com.android.support.test:rules:0.2')androidTestCompile('com.android.support.test.espresso:espresso-core:2.1')}
gradle同步时会提示
Warning:Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app and test app differ.
执行dependencies会提示
FAILURE: Build failed with an exception.* What went wrong:A problem occurred configuring project ':app'.> Conflict with dependency 'com.android.support:support-annotations'. Resolved versions for app and test app differ.* Try:Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.BUILD FAILED
不兼容
虽然可以通过force、exclude等方式避免依赖项版本冲突,使得grade同步成功,但是并不能代表编译时没有问题。由于不同版本可能不完全兼容,于是会出现各种奇怪的报错。已知的解决思路是更改包的版本、尝试强制使用不同版本的依赖项,找到可兼容的依赖组合。
报错例如:
com.android.dex.DexException: Multiple dex files define Lorg/hamcrest/MatcherAssert;at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)at com.android.dx.command.dexer.Main.runMonoDex(Main.java:303)at com.android.dx.command.dexer.Main.run(Main.java:246)at com.android.dx.command.dexer.Main.main(Main.java:215)at com.android.dx.command.Main.main(Main.java:106)Error:Execution failed for task ':app:dexDebugAndroidTest'.> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java'' finished with non-zero exit value 2BUILD FAILED
又例如Android执行Espresso单元测试时出现:
Running testsTest running startedjava.lang.NoSuchMethodError: org.hamcrest.core.AnyOf.anyOfat org.hamcrest.Matchers.anyOf(Matchers.java:87)at android.support.test.espresso.Espresso.<clinit>(Espresso.java:158)at com.jzj1993.unittest.test.MainActivityEspressoTest.sayHello(MainActivityEspressoTest.java:28)at java.lang.reflect.Method.invokeNative(Native Method)at java.lang.reflect.Method.invoke(Method.java:525)at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)at android.support.test.internal.statement.UiThreadStatement.evaluate(UiThreadStatement.java:55)at android.support.test.rule.ActivityTestRule$ActivityStatement.evaluate(ActivityTestRule.java:257)at org.junit.rules.RunRules.evaluate(RunRules.java:18)at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)at org.junit.runners.ParentRunner.run(ParentRunner.java:300)at org.junit.runners.Suite.runChild(Suite.java:128)at org.junit.runners.Suite.runChild(Suite.java:24)at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)at org.junit.runners.ParentRunner.run(ParentRunner.java:300)at org.junit.runner.JUnitCore.run(JUnitCore.java:157)at org.junit.runner.JUnitCore.run(JUnitCore.java:136)at android.support.test.internal.runner.TestExecutor.execute(TestExecutor.java:54)at android.support.test.runner.AndroidJUnitRunner.onStart(AndroidJUnitRunner.java:228)at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)Finish
参考资料与扩展阅读
https://docs.gradle.org/current/userguide/dependency_management.html
http://www.concretepage.com/build-tools/gradle/gradle-exclude-transitive-dependency-example
Gradle依赖项学习总结,dependencies、transitive、force、exclude的使用与依赖冲突解决的更多相关文章
- “未能加载文件或程序集“XXX”或它的某一个依赖项。试图加载格式不正确的程序”问题的解决
发布到win7 64位旗舰版iis上时,报:“未能加载文件或程序集“BC.Common”或它的某一个依赖项.试图加载格式不正确的程序”. 该DLL的本地复制没有设置为true(在项目引用里找到该引用, ...
- 学习WPF——初识依赖项属性
入门 首先创建一个依赖项属性 然后绑定父容器的DataContext到这个依赖项的实例 接着绑定子元素的属性到依赖项属性(注意Button的Content属性) 程序最终的运行结果: 说明 首先是 ...
- WPF中的依赖项属性
Form cnblogs 桂素伟 随着WPF的推广,不得不重新拾起WPF来,因为这块的产品越来越多. 只能跟着MSDN来学了,所以想是在这里记录下学习的过程和对知识的理解. 先从最基本的吧,依赖项属性 ...
- WPF中的依赖项属性(转)
出处:https://www.cnblogs.com/axzxs2001/archive/2010/04/25/1719857.html 随着WPF的推广,不得不重新拾起WPF来,因为这块的产品越来越 ...
- WPF教程五:附加依赖项属性
附加依赖项属性是一个属性本来不属于对象自己,但是某些特定场景其他的对象要使用该对象在这种场景下的值.这个值只在这个场景下使用.基于这个需求设计出来的属性.这里主要涉及到一个解耦问题.最大的优势是在特定 ...
- 未能加载文件或程序集“System.Web.Http.WebHost, Version=4.0.0.0, ”或它的某一个依赖项。系统找不到指定的文件。
一:错误提示 "未能加载文件或程序集"System.Web.Http.WebHost, Version=4.0.0.0, Culture=neutral, PublicKeyTok ...
- 安装SQL2008时遇到"未能加载文件或"file:///d:microsoft..sql.chainer.packagedata.dll"或它的某个依赖项
安装SQL2008时遇到"未能加载文件或"file:///d:microsoft..sql.chainer.packagedata.dll"或它的某个依赖项,如下图所示 ...
- 浅谈WPF依赖项属性
浅谈WPF依赖项属性 0. 引言 依赖项属性虽然在使用上和CLR属性一样,但是它是WPF特有的,不同于CLR属性.只是封装为我们常用CLR的属性,在语法使用上和CLR属性一样.WPF中一些功能:动画, ...
- .NET Core TDD 前传: 编写易于测试的代码 -- 依赖项
第1篇: 讲述了如何创造"缝". "缝"(seam)是需要知道的概念. 第2篇, 避免在构建对象时写出不易测试的代码. 本文是第3篇, 讲述依赖项和迪米特法则 ...
随机推荐
- uCGUI的文字与数值显示方法
uCGUI的数值显示非常的灵活方便,是制作LCD界面非常好的选择. 文字与数值显示的方法: 常用文本显示函数: void GUI_DispStringAt(const char GUI_FAR *s, ...
- perl脚本之目录
来源: http://www.cnblogs.com/itech/archive/2013/02/20/2919204.html http://stackoverflow.com/questions/ ...
- Inno Setup入门(十八)——Inno Setup类参考(4)
分类: Install Setup 2013-02-02 11:29 406人阅读 评论(0) 收藏 举报 编辑框 编辑框也叫文本框,是典型的窗口可视化组件,既可以用来输入文本,也可以用来显示文本,是 ...
- idea 端口占用
netstat -anp | grep 8080 lsof -i:8080 查看8080端口被什么进程占用 kill (-s 9) 12903 -s 9 强制 尽快 12903 上面查出的 PID 其 ...
- Anton and Making Potions
Anton and Making Potions time limit per test 4 seconds memory limit per test 256 megabytes input sta ...
- Android OpenGL ES(三)OpenGL ES API 命名习惯 .
OpenGL ES是个跨平台的3D图形开发包规范,最常见的实现是采用C语言实现的,Android OpenGL ES 实现上是使用Java 语言对底层的C接口进行了封装,因此在android.open ...
- oracle 锁表的处理。
最近系统每天经常锁表,进程杀死后,很快再次锁住这个表. (一)先贴出现场处理死锁的步骤. 另外:有时候通过PL/SQL执行kill session可能仍然无法解锁,此时需要登陆到Oracle服务器将进 ...
- OVS - commands
journalctl -t ovs-vswitchd ovs-vsctl show ovs-ofctl show br0 set vlanid ovs-vsctl set port eth0 tag= ...
- GameUnity 2.0 文档(五) 人工智能之---------------Flocking算法 (聚集,分散,列队 )
AI是游戏的灵魂,是人物的智商,是让玩家觉得游戏是否幼稚的重要判断功能,下面我将介绍国外流行,国内不行的,ai算法. 主要介绍 Flocking 和 Reciprocal Velocity Obs ...
- display:block;inline;inline-block大总结
总体概念 block和inline这两个概念是简略的说法,完整确切的说应该是 block-level elements (块级元素) 和 inline elements (内联元素).block元素通 ...