# Latest.release OR latest.integration : getting across multiple repositories : seems to pick the first repo only
**URL:** https://discuss.gradle.org/t/latest-release-or-latest-integration-getting-across-multiple-repositories-seems-to-pick-the-first-repo-only/26994
**Category:** Help/Discuss
**Created:** [May 18, 2018, 2:15pm UTC](https://discuss.gradle.org/t/latest-release-or-latest-integration-getting-across-multiple-repositories-seems-to-pick-the-first-repo-only/26994 "2018-05-18T14:15:14Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@hanasaki](https://discuss.gradle.org/u/hanasaki)
#### Post date: [May 18, 2018, 2:15pm UTC](https://discuss.gradle.org/t/latest-release-or-latest-integration-getting-across-multiple-repositories-seems-to-pick-the-first-repo-only/26994/1 "2018-05-18T14:15:14Z")
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
mavenCentral
It seems that IF any version is found in mavenLocal, mavenCentral is not consulted at all.
---
### Author:  [@fredc](https://discuss.gradle.org/u/fredc)
#### Post date: [May 18, 2018, 6:37pm UTC](https://discuss.gradle.org/t/latest-release-or-latest-integration-getting-across-multiple-repositories-seems-to-pick-the-first-repo-only/26994/2 "2018-05-18T18:37:35Z")
I thought this was fixed a while ago, but I may be wrong. Have you tried with a recent Gradle version?
---
### Author:  [@hanasaki](https://discuss.gradle.org/u/hanasaki)
#### Post date: [May 25, 2018, 3:09pm UTC](https://discuss.gradle.org/t/latest-release-or-latest-integration-getting-across-multiple-repositories-seems-to-pick-the-first-repo-only/26994/3 "2018-05-25T15:09:22Z")
experienced it in gradle 4.7