[GRADLE-3331] Changed ordering of resolved dependency artifacts Created: 10/Aug/15  Updated: 10/Aug/15  Resolved: 10/Aug/15

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 2.6-rc-2

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Fixed Votes: 0

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.

Generated at Wed Jun 30 12:46:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.