为什么 Android 将 Gradle 依赖项中的“编译"配置更改为“实现"配置? [英] Why Android change 'compile' to 'implementation' configuration in Gradle dependencies?

问题描述

正如在 Android Studio 3.0 (canary 3.0) 中所见，我们现在通过声明 implementation 而不是 compile 配置来添加 depedencies.

As seen in Android Studio 3.0 (canary 3.0), we now add depedencies by declaring implementation instead of compile configuration.

// Before
compile 'com.android.support:appcompat-v7:25.3.1'

// Currently
implementation 'com.android.support:appcompat-v7:25.3.1'

我们仍然可以使用compile，但我想了解一下:

We can still use compile, but I would like to understand:

• implementation 和 compile 配置有什么区别?
• 为什么 Android Gradle 构建更改为默认使用 implementation?

• What is the difference between implementation and compile configuration?
• Why do Android Gradle build change to use implementation as default?

推荐答案

compile 似乎已被弃用，api 或 implementation 应该改为使用.根据 Java 库插件 - Gradle 用户指南 3.5 版:

It seems like compile has been deprecated and api or implementation should be used instead. According to The Java Library Plugin - Gradle User Guide Version 3.5:

compile 配置仍然存在，但不应使用，因为它不会提供 api 和 implementation 配置提供的保证.

The compile configuration still exists but should not be used as it will not offer the guarantees that the api and implementation configurations provide.

这篇关于为什么 Android 将 Gradle 依赖项中的“编译"配置更改为“实现"配置?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！