Android studio 0.5.9:2 个恼人的 Gradle 警告 [英] Android studio 0.5.9: 2 annoying Gradle warnings
问题描述
我已升级到 Android Studio 0.5.9，但总是收到以下警告:
I've upgraded to Android Studio 0.5.9 and am always getting these warnings:
Configuration on demand is an incubating feature.
Relying on packaging to define the extension of the main artifact has been deprecated and is scheduled to be removed in Gradle 2.0
有什么我应该做的吗?如果没有，我可以禁用它们吗?
is there anything I'm supposed to about it? If not, can I disable them?
推荐答案
谷歌搜索 Gradle 孵化功能 结果 此页面:
C.1.2.孵化
在孵化状态下引入功能以允许现实世界在公开之前将反馈纳入该功能并锁定以提供向后兼容性.它也给愿意接受未来潜在变化的用户提前访问以便他们可以立即投入使用.
Features are introduced in the incubating state to allow real world feedback to be incorporated into the feature before it is made public and locked down to provide backwards compatibility. It also gives users who are willing to accept potential future changes early access to the feature so they can put it into use immediately.
处于孵化状态的功能可能会在未来的 Gradle 版本中发生变化直到它不再孵化.孵化功能的变化Gradle 版本将在发行说明中突出显示释放.新功能的潜伏期因人而异功能的范围、复杂性和性质.
A feature in an incubating state may change in future Gradle versions until it is no longer incubating. Changes to incubating features for a Gradle release will be highlighted in the release notes for that release. The incubation period for new features varies depending on the scope, complexity and nature of the feature.
孵化中的特征清楚地表明是这样.在源代码，所有正在孵化的方法/属性/类都有注释带有 Incubating，也用于在 DSL 中专门标记它们和 API 参考.如果此用户中讨论了孵化功能引导，会明确表示处于孵化状态.
Features in incubation are clearly indicated to be so. In the source code, all methods/properties/classes that are incubating are annotated with Incubating, which is also used to specially mark them in the DSL and API references. If an incubating feature is discussed in this User Guide, it will be explicitly said to be in the incubating state.
<小时>
Searching for 依赖打包来定义主要工件的扩展已被弃用，并计划在 Gradle 2.0 中移除 导致这个问题，如@shayan Pourvatan 所述:
Searching for Relying on packaging to define the extension of the main artifact has been deprecated and is scheduled to be removed in Gradle 2.0 results in this question as @shayan pourvatan stated:
Gradle 弃用 "依靠打包来定义主神器的外延……"在 Android Studio 项目中可以修复吗?
和这个问题，它在结束:
基于 http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c Gradleware 团队的一名成员说目前没有办法绕过警告，但警告是假的."
Based on http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c a member of the Gradleware team said "There's no way around the warning at the moment, but the warning is bogus."
所以我们现在无能为力.
So there is nothing we can do right now.
这篇关于Android studio 0.5.9:2 个恼人的 Gradle 警告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
