mikehearn07/28/2022, 1:52 PM
? This just started now so I'm wondering if someone accidentally yanked an artifact from some repository. Not sure what the best channel to ask about this is.
Unable to find a variant of org.jetbrains.kotlin:kotlin-test:1.6.10
tapchicoma07/28/2022, 1:56 PM
mikehearn07/28/2022, 1:57 PM
(there is no stack trace, I can use the --stacktrace flag if you want)
> Could not resolve all files for configuration ':hydraulic.conveyor.tools.pom2json:testRuntimeClasspath'. > Could not resolve org.jetbrains.kotlin:kotlin-test:1.6.10. Required by: project :hydraulic.conveyor.tools.pom2json > Unable to find a variant of org.jetbrains.kotlin:kotlin-test:1.6.10 providing the requested capability org.jetbrains.kotlin:kotlin-test-framework-junit5: - Variant compile provides org.jetbrains.kotlin:kotlin-test:1.6.10 - Variant runtime provides org.jetbrains.kotlin:kotlin-test:1.6.10 - Variant platform-compile provides org.jetbrains.kotlin:kotlin-test-derived-platform:1.6.10 - Variant platform-runtime provides org.jetbrains.kotlin:kotlin-test-derived-platform:1.6.10 - Variant enforced-platform-compile provides org.jetbrains.kotlin:kotlin-test-derived-enforced-platform:1.6.10 - Variant enforced-platform-runtime provides org.jetbrains.kotlin:kotlin-test-derived-enforced-platform:1.6.10
tapchicoma07/28/2022, 1:58 PM
mikehearn07/28/2022, 2:00 PM
mbonnin07/28/2022, 2:02 PM
mikehearn07/28/2022, 2:21 PM
Vampire07/28/2022, 4:30 PM
mikehearn07/28/2022, 5:33 PM
had been placed above
. Didn't matter until today - presumably recently I opened a project that resolved kotlin-test into the local repository, at which point Gradle started finding the artifacts but not the gradle .module file. It was confusing because the error message does name some variants that the artifact exports so it took a while to think of this, as there's no useful debug logging that showed where it was trying to resolve from. Presumably, the variants it names are synthetic.
Vampire07/28/2022, 5:36 PM
if possible. And if you really need to, then you should at least use a repository content filter to only take things from there you know are good. Maven local repository is broken by design. It is not a pure repository, it is a mixture of repository and cache for Maven. So as soon as a Maven project requested some file it is cached there, and then Gradle sees a broken state like you observed.
Paul Woitaschek07/30/2022, 1:25 PM
for everything but mavenCentral and google
gildor08/01/2022, 3:55 PM
ilya.gorbunov08/01/2022, 5:43 PM
Vampire08/01/2022, 5:50 PM
ilya.gorbunov08/01/2022, 5:57 PM
repository declared above the repo from which the artifacts should have been resolved.
Vampire08/01/2022, 6:00 PM