Require users to disable configure-on-demand if using Gradle 4.6 or later [AGP 3.1.2 only] [77910727]

Fixed

Bug

Status Update

No update yet.

Description

hu...@google.com

created issue #1

Apr 11, 2018 06:55PM

From

Issue 76429932

: "Gradle's handling of 4.6 breaks our bypass for dynamically computed file collection and supplier when using Configure on Demand. We will fix this for 3.2 but we need to document this. When using Gradle 4.6 with Android Gradle plugin 3.0.x and 3.1, users should not enable Configure On Demand."

We'll need to detect the case above, fail the build, and ask users to disable configure-on-demand.

Comments

hu...@google.com <hu...@google.com> #2Apr 11, 2018 10:28PM

This applies to Android Gradle plugin 3.1.2 only. It's okay to use configure-on-demand with AGP 3.2.x.

CL is pending review: Change-Id Ia7d9756a8d8ff83a3a08355dce8946f38c09276e

hu...@google.com <hu...@google.com> Apr 12, 2018 04:48PM

Marked as fixed.

ko...@google.com <ko...@google.com> #3Apr 12, 2018 08:02PM

This is documented in the known issues here:

https://developer.android.com/studio/known-issues.html

Issue 77910727

Description

Issue summary

Comments

hu...@google.com <hu...@google.com> #2Apr 11, 2018 10:28PM

hu...@google.com <hu...@google.com> Apr 12, 2018 04:48PM

ko...@google.com <ko...@google.com> #3Apr 12, 2018 08:02PM

Add comment

Issue metadata