Cannot resolve external dependency org.jetbrains.kotlin:kotlin-stdlib

Hello, Ruth!

Thank you for reporting this!

How the repositories are defined for your Project?

Try listing the repositories Gradle aware of when running it from OS Command Prompt and from IDEA (this Stack Overflow Thread explains how it can be done).

As a workaround, try starting IDEA from OS Command Prompt with idea command.

Roman Vatagin many thanks for your message. On the console I get the following list:

Name: github; url: https://maven.pkg.github.com/orga1/.github
Name: github2; url: https://maven.pkg.github.com/<orga2/.github
Name: MavenRepo; url: https://repo.maven.apache.org/maven2/
Starting it with the idea command unfortunately did not change anything

Ruth Bassindale Maven Central definitely does have the Artifact.

Does Gradle return the same list of the repositories when you run it from IDEA?

Could you try running the build with --info flag in IDEA and share the full output?

Roman Vatagin I assume you mean if I run it you mean the gradle tab and then under tasks click on `build`?

I did that and there is no error either. the repositories shown there are the same as via the console. 

So Only the loading of the Gradle projects seem to be problematic.

Ruth Bassindale This is curious!

How the repositories are declared in the Project? What version of Gradle does it use?

Would you be able to share the Project for further investigation?

I gutted the project as it is closed source, but with this gutted project I still get that error.

You can find it here

Ruth Bassindale Thank you for sharing the Project!

Looking closely into it, the root Project (leadtools-backend) does not have any repositories defined. I'm guessing it is only used as an aggregator for its' Subprojects.

Adding repositories section to its' build.gradle.kts:

repositories {
    mavenCentral()
}

seems to resolve the issue.

But all other services we have (>50) are defined like that and there is no problem, only kotlin2.0 seems to have broken that system

Also the plugin is only applied to the subprojects not the rootProject.

But as you said, moving the repositories from the `subProjects` to the `allProjects` section solves it. I just do not understand why?

Ruth Bassindale I've done some more testing on this and the issue does seem to be specific to Kotlin 2.x, I have been also able to reproduce it with version 1.9.25.

I'm guessing dependencies for the earlier version of Kotlin Plugin that your Project used to use were already present in your local Gradle caches, so they did not have to be downloaded.

When you upgraded to Kotlin Plugin 2.0.10, it had a different set of dependencies or more likely same dependencies, but different versions of them, i .e. org.jetbrains.kotlin:kotlin-stdlib:2.0.10.

Those Artifacts were not present in Gradle caches and had to be downloaded and this is how the issue manifested itself.