This message was deleted.

I think the repo order is based on the order in the repositories block

you can also use

content { }

to control what comes from each repo

Yes, was my guess too. But I think that gradle chooses always the latest possible version across all repos. That is not what i want in my case

it shouldn't just magically upgrade to the latest version unless that's what you (or a dependency) asks for, so to an extent I don't understand your case to begin with

I'll just explain what I semantically want to do 🙂 At work, we have a "staging" repo and a "normal" repo. Usually, we wanna use the "normal" repo. But sometimes, we want to checkout new features in our testenv. Do do that, we push artifacts to the staging repo. Unfortunately, the artifact versions in the "staging" repo are lower than the versions in the "normal" repo. This is not directly under my control. And I also can't hard-code that gradle shall only search in "staging" since I don't know, for which dependencies a staging version exists beforehand. Therefore, I want gradle to prefer artifacts from "staging", even if there is a newer version in "normal".