This message was deleted.
# dependency-managements
Slackbot
04/26/2022, 9:07 PMThis message was deleted.
t
Tapchicoma
04/26/2022, 9:16 PMSeems related: https://github.com/gradle/gradle/issues/1629
c
CristianGM
04/26/2022, 9:56 PMOuch, it's seems like a hard to fix issue.
You would need to rename the dependency so Gradle doesn't need to resolve the version conflict. I guess that's what one of the last messages in the issue suggest using an includedBuild, that at the end is just a wrapper to rename the artifact.
l
Louis Jacomet
04/27/2022, 6:01 AMCurrently Gradle always puts the current project as the root of the dependency graph. And that root will substitute itself to all matching coordinates.
So you will have to perform the resolution in a different project - that is somewhere where the root has different coordinates.
Adding a feature where you could say that the root is something else and thus resolve older version of the same project has been asked but is not yet implemented.