Android的工作室0.5.9:2恼人的摇篮警告 [英] Android studio 0.5.9: 2 annoying Gradle warnings

查看:182
本文介绍了Android的工作室0.5.9:2恼人的摇篮警告的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经升级到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?

推荐答案

在谷歌搜索摇篮孵化功能的结果的此页面

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.

在一个孵化状态的功能,在未来的摇篮版本可能会改变   直到它不再孵育。更改为一个孵化功能   摇篮版本将在该发行说明中加以强调   推出。潜伏期为新的特性的变化取决于   特征的范围,复杂性和性质。

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.

在孵化功能都清楚地表明是如此。在源   code,被孵化的所有方法/属性/类注释   与孵化,它也用于在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.

搜索依靠包装来定义主神器的扩展已经pcated德$ P $,并计划在摇篮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:

<一个href="http://stackoverflow.com/questions/21496956/gradle-de$p$pcation-relying-on-packaging-to-define-the-extension-of-the-main-art">Gradle德precation&QUOT;依靠包装来定义主神器的延伸...&QUOT;在Android的Studio项目可以是固定的?

这个问题,它说这个底:

href="http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c">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的工作室0.5.9:2恼人的摇篮警告的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆