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.

更新：

和我的老朋友 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索引。

您所要做的只是什么，只是下一个Fabric Plugin版本的w8。

Answer 1

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

  

android.debug.obsoleteApi = true

visit this link..