[GRADLE-3331] Changed ordering of resolved dependency artifacts Created: 10/Aug/15 Updated: 10/Aug/15 Resolved: 10/Aug/15
|Known Issue Of:|
While the order of resolved artifacts is not strictly part of the Gradle compatibility contract, changes to classpath ordering can cause compilation issues that are hard to diagnose.
Gradle 2.5 introduced a change that caused the order of classpath artifacts to be different for certain dependency configurations. This change has been reverted in Gradle 2.6.