What does it mean for a gradle property to be “experimental and unsupported”?
Several times, to solve an issue or update dependencies, I had to enable a given gradle option setting.
For example, Robolectric 4.0 Migration guide states:
Put this in your gradle.properties:
android.enableUnitTestBinaryResources=true
Likewise, to debug a databinding compile error I followed the advice printed in Gradle's build log:
Gradle may disable incremental compilation [...].
Consider setting the experimental feature flagandroid.enableSeparateAnnotationProcessing=truein the gradle.properties file to run annotation processing in a separate task and make compilation incremental.
From both examples, I get that the authors (Robolectric/gradle maintainers) are confident that enabling this option will have a positive impact on each situation.
However, in both cases I get this warning in my build output:
WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.
The current default is 'false'.
WARNING: The option setting 'android.enableSeparateAnnotationProcessing=true' is experimental and unsupported.
The current default is 'false'.
I had in my gradle.properties since a few months the flag android.databinding.enableV2=true. To see how it's handled, I tried to put it to false, which brought the same The option setting 'android.databinding.enableV2=false' is experimental and unsupported. warning (which seems to suggest an unsupported setting is ignored).
I understand these are experimental feature flags. But what about unsupported? Does this mean I should not expect support if anything goes wrong, or does it mean they will be ignored?
If it means they are ignored, how are those properties meant to be used?
android gradle android-databinding gradle-properties asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
add a comment |
Several times, to solve an issue or update dependencies, I had to enable a given gradle option setting.
For example, Robolectric 4.0 Migration guide states:
Put this in your gradle.properties:
android.enableUnitTestBinaryResources=true
Likewise, to debug a databinding compile error I followed the advice printed in Gradle's build log:
Gradle may disable incremental compilation [...].
Consider setting the experimental feature flagandroid.enableSeparateAnnotationProcessing=truein the gradle.properties file to run annotation processing in a separate task and make compilation incremental.
From both examples, I get that the authors (Robolectric/gradle maintainers) are confident that enabling this option will have a positive impact on each situation.
However, in both cases I get this warning in my build output:
WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.
The current default is 'false'.
WARNING: The option setting 'android.enableSeparateAnnotationProcessing=true' is experimental and unsupported.
The current default is 'false'.
I had in my gradle.properties since a few months the flag android.databinding.enableV2=true. To see how it's handled, I tried to put it to false, which brought the same The option setting 'android.databinding.enableV2=false' is experimental and unsupported. warning (which seems to suggest an unsupported setting is ignored).
I understand these are experimental feature flags. But what about unsupported? Does this mean I should not expect support if anything goes wrong, or does it mean they will be ignored?
If it means they are ignored, how are those properties meant to be used?
android gradle android-databinding gradle-properties asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
Quoting from the "Known Issues" from here :Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.
– ZeekHuge
Nov 25 '18 at 19:13
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12
add a comment |
Several times, to solve an issue or update dependencies, I had to enable a given gradle option setting.
For example, Robolectric 4.0 Migration guide states:
Put this in your gradle.properties:
android.enableUnitTestBinaryResources=true
Likewise, to debug a databinding compile error I followed the advice printed in Gradle's build log:
Gradle may disable incremental compilation [...].
Consider setting the experimental feature flagandroid.enableSeparateAnnotationProcessing=truein the gradle.properties file to run annotation processing in a separate task and make compilation incremental.
From both examples, I get that the authors (Robolectric/gradle maintainers) are confident that enabling this option will have a positive impact on each situation.
However, in both cases I get this warning in my build output:
WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.
The current default is 'false'.
WARNING: The option setting 'android.enableSeparateAnnotationProcessing=true' is experimental and unsupported.
The current default is 'false'.
I had in my gradle.properties since a few months the flag android.databinding.enableV2=true. To see how it's handled, I tried to put it to false, which brought the same The option setting 'android.databinding.enableV2=false' is experimental and unsupported. warning (which seems to suggest an unsupported setting is ignored).
I understand these are experimental feature flags. But what about unsupported? Does this mean I should not expect support if anything goes wrong, or does it mean they will be ignored?
If it means they are ignored, how are those properties meant to be used?
android gradle android-databinding gradle-properties asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
Several times, to solve an issue or update dependencies, I had to enable a given gradle option setting.
For example, Robolectric 4.0 Migration guide states:
Put this in your gradle.properties:
android.enableUnitTestBinaryResources=true
Likewise, to debug a databinding compile error I followed the advice printed in Gradle's build log:
Gradle may disable incremental compilation [...].
Consider setting the experimental feature flagandroid.enableSeparateAnnotationProcessing=truein the gradle.properties file to run annotation processing in a separate task and make compilation incremental.
From both examples, I get that the authors (Robolectric/gradle maintainers) are confident that enabling this option will have a positive impact on each situation.
However, in both cases I get this warning in my build output:
WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.
The current default is 'false'.
WARNING: The option setting 'android.enableSeparateAnnotationProcessing=true' is experimental and unsupported.
The current default is 'false'.
I had in my gradle.properties since a few months the flag android.databinding.enableV2=true. To see how it's handled, I tried to put it to false, which brought the same The option setting 'android.databinding.enableV2=false' is experimental and unsupported. warning (which seems to suggest an unsupported setting is ignored).
I understand these are experimental feature flags. But what about unsupported? Does this mean I should not expect support if anything goes wrong, or does it mean they will be ignored?
If it means they are ignored, how are those properties meant to be used?
android gradle android-databinding gradle-properties android gradle android-databinding gradle-properties asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
asked Nov 15 '18 at 15:31
PLNechPLNech
2,0871435
2,0871435
Quoting from the "Known Issues" from here :Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.
– ZeekHuge
Nov 25 '18 at 19:13
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12
add a comment |
Quoting from the "Known Issues" from here :Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.
– ZeekHuge
Nov 25 '18 at 19:13
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12
Quoting from the "Known Issues" from here :
Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.– ZeekHuge
Nov 25 '18 at 19:13
Quoting from the "Known Issues" from here :
Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.– ZeekHuge
Nov 25 '18 at 19:13
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322771%2fwhat-does-it-mean-for-a-gradle-property-to-be-experimental-and-unsupported%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322771%2fwhat-does-it-mean-for-a-gradle-property-to-be-experimental-and-unsupported%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Quoting from the "Known Issues" from here :
Android Gradle Plugin may report the following warning, which may be safely ignored: WARNING: The option setting 'android.enableUnitTestBinaryResources=true' is experimental and unsupported.. Android Gradle Plugin 3.3 will resolve this issue.– ZeekHuge
Nov 25 '18 at 19:13
Also, for me, migrating to androidX removed those warnings at all !
– ZeekHuge
Nov 25 '18 at 21:02
@ZeekHuge thanks for your comments. I have read this paragraph, which seems to imply this option is ignored, but is it the case for all "experimental and unsupported" option settings?
– PLNech
Nov 26 '18 at 12:12