Classpath order is not deterministic with Gradle 3.1 RC1

[Alexey_Tsvetkov]

Git repo: https://github.com/tsvtkv/android-dagger
It’s an android project that uses kotlin and dagger.
I’ve added classpath printing to kotlin and java tasks (in doFirst).
Running ‘assembleDebug’ multiple times, I’ve noticed that classpath order is often different (which forces Kotlin compilation).

Gradle Version: 3.1 RC1
Operating System and JVM version: Ubuntu 14.04 64 bit; JDK 1.8.0_102

The issue does not seem reproducible for me with Gradle 2.14.1 and Gradle 3.0.

[jendrik (Jendrik Johannes)]

Sounds similar to:

Since 3.0, classpath order of Android project isn't consistent

Gradle Version: 3.0 Operating System and JVM version: Windows 10 64 Bit, 1.8.0_60 64 bit AFAIK, Gradle guarantees that the compilation classpath will have a consistent (while arbitrary in regards to transitive dependencies) order. It seems that starting with Gradle version 3.0, the order of the classpath entries of an Android project isn’t consistent anymore. This is a problem when using the Kotlin plugin because it breaks incremental compilation. I summarized the problem in https://code.goog…

Could there be something else (a configuration change with the switch to 3.1 RC1) that could have caused the new behaviour? It seems the issue (or a similar issue) exists for longer already and it might be a problem with the Android plugin: Google Issue Tracker