Latest.release OR latest.integration : getting across multiple repositories : seems to pick the first repo only

(hanasaki jiji) #1

Does latest.release OR latest.integration, or a version depend like 1.2.+ get the highest number checking across all repos? For example, the build has
mavenLocal followed by

It seems that IF any version is found in mavenLocal, mavenCentral is not consulted at all.

(Fred Curts) #2

I thought this was fixed a while ago, but I may be wrong. Have you tried with a recent Gradle version?

(hanasaki jiji) #3

experienced it in gradle 4.7