Android Gradle Implementation vs CompileOnly Performance(Android Gradle 实现与 CompileOnly 性能)
问题描述
性能?
我认为 api
需要更多内存,因为 gradle 将快照该 transitive module 中的每个类,反之亦然implementation
是首选配置,因为(如上所述)它用于自己的内部实现.
The docs mention that implementation
provides significant build time improvements over compile
/api
. What about compileOnly
?
My use case is a multi-module (sorry I don't like Gradle's multi-project terminology) project, where I have an Android app, and multiple libraries that the app depends on (implementation
). Some of the libraries also depend on one another. Should I use implementation
or compileOnly
when declaring dependencies in the library modules? My app module will be using implementation
to depend on those artifacts, so I don't need them to be transitive through the library modules.
The api
configuration should be used for dependencies that are exported to external modules
(transitive dependency). Vice-Versa implementation
configuration should be used for dependencies that are internal to the component (not transitive dependency).
implementation vs compileOnly:
There is no similarity in their job, compileOnly
is
- a configuration inherited from java-plugin
- required at compile time
- also not included in the runtime classpath or exposed to dependent projects.
So compileOnly
doesn't replace the implementation
configuration job e.g:
implementation 'com.android.support:appcompat-v7:25.1.0' // can't use compileOnly here
testCompile 'junit:junit:4.12'
compile "com.google.dagger:dagger:2.8" // can't use here also
annotationProcessor "com.google.dagger:dagger-compiler:2.8" // can't use here also
compileOnly 'javax.annotation:jsr250-api:1.0' // we can use compileOnly here because it's required on run time only.
Since your case is a "multi-module", you have to use the api
configuration, until you reach the final module it's better to use implementation
.
Following graph describe those configurations:
Performance?
I think api
requires more memory because gradle will snapshot every class in that transitive module, vice versa implementation
is a preferred configuration because (as mentioned above) it's used for its own internal implementations.
这篇关于Android Gradle 实现与 CompileOnly 性能的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:Android Gradle 实现与 CompileOnly 性能


基础教程推荐
- NSString intValue 不能用于检索电话号码 2022-01-01
- Cocos2d iPhone 非矩形精灵触摸检测 2022-01-01
- navigator.geolocation.getCurrentPosition 在 Android 浏览器上 2022-01-01
- iPhone - 获取给定地点/时区的当前日期和时间并将其与同一地点的另一个日期/时间进行比较的正确方法 2022-01-01
- Android:getLastKnownLocation(LocationManager.NETWORK_PROVIDER 2022-01-01
- AdMob 广告未在模拟器中显示 2022-01-01
- libGDX 从精灵或纹理中获取像素颜色 2022-01-01
- iOS4 创建后台定时器 2022-01-01
- 通过重定向链接在 Google Play 中打开应用 2022-01-01
- 如何从 logcat 中删除旧数据? 2022-01-01