gradle-versions-plugin: "Failed to resolve" when using in multi-module project and gradle 5.6
When I start the task in the root project, I get these errors before the report is generated:
Failed to resolve :module1:debugAndroidTestCompileClasspath
Failed to resolve :module1:debugCompileClasspath
Failed to resolve :module1:debugUnitTestCompileClasspath
Failed to resolve :module1:releaseCompileClasspath
Failed to resolve :module1:releaseUnitTestCompileClasspath
Failed to resolve :module2:debugAndroidTestCompileClasspath
Failed to resolve :module2:debugCompileClasspath
Failed to resolve :module2:debugUnitTestCompileClasspath
Failed to resolve :module2:releaseCompileClasspath
Failed to resolve :module2:releaseUnitTestCompileClasspath
....
I am defining my dependencies in a buildSrc module via the Kotlin dsl and then use those defined dependencies in all other modules. Could this cause that error? Is this a known error and can it be fixed?
Thanks!
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 20 (10 by maintainers)
Thanks for the quick reply. I was using an old version of the plugin (and it obviously couldn’t tell me that it was outdated). On the latest version, everything works fine (even on a multi-module project). But if you’re still interested, this was the exception (thrown for every “Failed to resolve”):
I have noticed that some repositories, like Sonatype’s snapshots repo, will rate limit queries and slow down resolution. Gradle now lets you specify that a repository only applies to certain artifacts to speed up searches. You might look at the info/debug logs if it becomes frustrating.