Library projects do not pick up changes with Gradle 2.14 [37105417]

Fixed

Bug

[AOSP] Released

Migrated-Tools-Gradle

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jun 17, 2016 11:32AM

Library projects require double builds to pick up changes, bundleRelease task is erroneously UP-TO-DATE the first time around.

This only happens with Gradle 2.14 (2.14-rc-1 inclusive). Bug was observed on Android Gradle plugin 1.5.0, 2.1.0, 2.1.2, 2.2.0-alpha3.

Steps to reproduce with the attached gradle-2.14-lib-bug.zip project:

1) ./gradlew :clean :bundleRelease
2) ./gradlew :bundleRelease
3) any change to Foo.java # example: sed -i '' 's/foo/bar/' src/main/java/Foo.java
4) ./gradlew :bundleRelease <-- bundleRelease is UP-TO-DATE, this is wrong

gradle-2.14-lib-bug.zip

71 KB

Download

Comments

be...@google.com <be...@google.com> Jun 17, 2016 03:38PM

Assigned to je...@google.com.

xa...@google.com <xa...@google.com> #2Jun 17, 2016 04:53PM

Additional details: on the 2nd call to bundleRelease, even though nothing changed, the bundlerelease task still runs with

Executing task ':bundleRelease' (up-to-date check took 0.001 secs) due to:
Input file /.../gradle-2.14-lib-bug/build/intermediates/bundles/release/libs has been added.
Input file /.../gradle-2.14-lib-bug/build/intermediates/bundles/release/jni has been added.
Input file /.../gradle-2.14-lib-bug/build/intermediates/bundles/release/classes.jar has been added.
:bundleRelease (Thread[Daemon worker,5,main]) completed. Took 0.009 secs.

So it looks like it's missing input changes the first time it runs after a change, but it's also broken when it runs a first no-op build right after a regular build.

xa...@google.com <xa...@google.com> #3Jun 17, 2016 04:55PM

BTW the bundleRelease task is a standard Gradle Zip task.

ma...@gmail.com <ma...@gmail.com> #4Jun 17, 2016 04:56PM

Yup, it looks as if the UP-TO-DATE status is from the *previous* build. Maybe it gets computed at configuration, not execution time? Would explain why it's always lagging behind.

xa...@google.com <xa...@google.com> #5Jun 17, 2016 05:16PM

I pinged the Gradle folks, because clearly it's on their end.

yo...@gmail.com <yo...@gmail.com> #6Jun 20, 2016 02:20PM

Is there an issue opened on the gradle bug tracker for this?

je...@google.com <je...@google.com> #7Jun 20, 2016 04:28PM

this is not a beta blocker, it is just preventing us from upgrading to 2.14 since Gradle broke the dependency management.

st...@gmail.com <st...@gmail.com> #8Jun 22, 2016 02:59AM

Here's the issue in the Gradle issue tracker:

https://issues.gradle.org/browse/GRADLE-3491

We're prepping a 2.14.1 to fix this.

ja...@google.com <ja...@google.com> #9Jun 24, 2016 04:54PM

Removing beta blocker flag as this is a Gradle issue. Workaround is to not use Gradle 2.14 for now.

je...@google.com <je...@google.com> #10Jun 30, 2016 03:54PM

Reassigned to ch...@google.com.

Raymond will own the Gradle 2.14.1 integration in both 2.1 and 2.2/dev branches.

ch...@google.com <ch...@google.com> #11Jul 8, 2016 10:26PM

Confirmed 2.14.1-rc-1 fixed the issue. Will update to 2.14.1 when released.

ja...@google.com <ja...@google.com> #12Jul 18, 2016 06:08PM

Marked as fixed.

Gradle 2.14.1 is now released. Please use that instead:

https://gradle.org/gradle-download/

Closing this bug.