android-studio - AGP 3.3 和 Gradle 5.0 警告已过时并将在 2019 年底删除

Question

我一直在使用 AS 3.3-rc1 和 AGP 3.3-rc1 并更新到 Gradle 5.0

从那以后我收到了这个警告。

有谁知道我怎样才能摆脱它们？

无法从 here 中找出任何东西和 here .

难道仅仅是因为它们是 RC 版本还是什么？

WARNING: API 'variant.getAssemble()' is obsolete and has been replaced with 'variant.getAssembleProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getAssemble(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variantOutput.getProcessResources()' is obsolete and has been replaced with 'variantOutput.getProcessResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variantOutput.getProcessResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variantOutput.getProcessManifest()' is obsolete and has been replaced with 'variantOutput.getProcessManifestProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variantOutput.getProcessManifest(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variant.getMergeResources()' is obsolete and has been replaced with 'variant.getMergeResourcesProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variant.getPackageApplication()' is obsolete and has been replaced with 'variant.getPackageApplicationProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getPackageApplication(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
WARNING: API 'variant.getExternalNativeBuildTasks()' is obsolete and has been replaced with 'variant.getExternalNativeBuildProviders()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
To determine what is calling variant.getExternalNativeBuildTasks(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.

更新:

通过我的老 friend Divide et Impera 方法，我找到了罪魁祸首，那就是 Fabric Gradle 插件

apply plugin: 'io.fabric'

期待他们的 github 仓库，看看是否已经有问题。

无论如何，我想从长远来看，只要fabric 使他们的插件符合新的 API，这些警告就会消失。

更新 2

与此相关的 Fabric GitHub 问题:

这是一般一:https://github.com/firebase/firebase-android-sdk/issues/230

这是索引较多的一个:https://github.com/firebase/firebase-android-sdk/issues/198由此索引 SO question .

您所要做的就是什么，只需 w8 即可用于下一个 Fabric 插件版本。

Answer 1

将以下行添加到 project/gradle/wrapper/Gradle-wrapper.properties .

android.debug.obsoleteApi=true