[GRADLE-3264] Gradle fails to resolve latest.status versions for some transitive dependencies Created: 17/Mar/15  Updated: 15/Jul/15  Resolved: 15/Jul/15

Status: Resolved
Project: Gradle
Affects Version/s: 2.2.1, 2.3
Fix Version/s: 2.4-rc-1

Type: Bug
Reporter: Sterling Greene Assignee: Unassigned
Resolution: Fixed Votes: 0


The situation I've been testing:

project has dependency on group:projectA:1.+
projectA has dependency on group:projectB:[1.1,1.2) and group:projectC:1.0.0.
projectB has no dependencies. All published versions have status=milestone.
projectC has dependency on group:projectB:latest.milestone.

In Gradle 2.3, this fails with a message that we cannot resolve group:projectB:latest.milestone. It should resolve to group:projectB:1.2 (taking the "newest" available when there's a conflict).

This also affects Gradle 2.2.1, and it may exist in older releases as well. This seems to be fixed in master (eventual 2.4). It was fixed somewhere between efe5422a79291b0c13d5509fb8e55 and faf38ce32958350c8cc0be57ac3cbfd54b4e8663.

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