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 性能
基础教程推荐
- Android:对话框关闭而不调用关闭 2022-01-01
- 如何在 UIImageView 中异步加载图像? 2022-01-01
- UIWebView 委托方法 shouldStartLoadWithRequest:在 WKWebView 中等效? 2022-01-01
- 在 gmail 中为 ios 应用程序检索朋友的朋友 2022-01-01
- Kivy Buildozer 无法构建 apk,命令失败:./distribute.sh -m “kivy"d 2022-01-01
- 如何让对象对 Cocos2D 中的触摸做出反应? 2022-01-01
- 当从同一个组件调用时,两个 IBAction 触发的顺序是什么? 2022-01-01
- 如何在没有IB的情况下将2个按钮添加到右侧的UINavigationbar? 2022-01-01
- android 应用程序已发布,但在 google play 中找不到 2022-01-01
- 如何在 iPhone 上显示来自 API 的 HTML 文本? 2022-01-01