Hello :wave: Anyone knows how Gradle determines pr...

# gradle

[Dariusz Kuc]

Hello 👋
Anyone knows how Gradle determines proper platform Kotlin module? i.e. what determines that Gradle picks up -jvm artifacts (e.g. given io.ktor:ktor-client-cio we expect io.ktor:ktor-client-cio-jvm to be picked up on JVM builds)?

[Vampire]

I guess by using the published Gradle metadata and variant-aware attribute-based resolution

[Vampire]

Here you have the module data for ktor-client-cio: https://repo1.maven.org/maven2/io/ktor/ktor-client-cio/1.5.0/ktor-client-cio-1.5.0.module

[Dariusz Kuc]

any idea what could break this resolution?

[Vampire]

break how?

[Dariusz Kuc]

https://kotlinlang.slack.com/archives/C19FD9681/p1610547344113500

[Dariusz Kuc]

since individual modules run correctly up to the Gradle plugin integration tests it somewhat points at the GradleRunner getting confused

[Vampire]

It more sounds like the Gradle Module metadata file is missing.

[Vampire]

Maybe you somehow get the lib into your maven local repository but without the module metadata and have mavenLocal() as repository?

[Vampire]

Then if the lib is in the maven local repo but without the module metadata, the resolution will fail

[Vampire]

But if the lib is not present in the maven local repo, then the next repositories are searched and then the one on maven central with the module metadata is found

[Vampire]

Just a wild guess though without having a look at your build

[Vampire]

Yep, many mavenLocal references in that repo, whyever

[Vampire]

And it always comes first, so if it is found there, it will be used

[Vampire]

And with ktor 1.3.1 there was no problem as it didn't yet publish the Gradle Module metadata back then

[Dariusz Kuc]

yeah i need maven local for the snapshot resolution for the maven integration tests

[Dariusz Kuc]

interestingly maven integration tests work fine

[Vampire]

Maven does not use the Gradle Module Metadata

[Dariusz Kuc]

my bad missed the Gradle part in the module metadata

[Vampire]

The problem is that you actually do maven integration tests probably, as those fill the maven local repository with the dependency without Gradle module metadata

[Dariusz Kuc]

any ideas how to work around this? I guess I could change the repo resolution order

[Vampire]

Sure two, just searching for the right syntax or link for the second, one moment

[Vampire]

One solution would be to put mavenLocal() in last position, not in first, as they are searched in order

[Dariusz Kuc]

yeah was going to try that

[Vampire]

The other that comes to my mind would be to use a repository content filter: https://docs.gradle.org/current/userguide/userguide_single.html#sec:declaring-repository-filter

[Dariusz Kuc]

👍

[Dariusz Kuc]

awesome! thanks for the help and pointers!

[Vampire]

With that you can exactly define what is searched for in a repository or is not searched for, so you could for example define that only snapshot versions are taken from maven local

[Vampire]

yw

[Vampire]

https://github.com/gradle/gradle/issues/15893

[Dariusz Kuc]

Thank you!

[Dariusz Kuc]

Just verified it and it works as expected, thanks again