Donát Csikós

I tried reproducing your issue, but for me the distribution url was picked up correctly: I'd like to investigate further. Please provide precise steps on how to reproduce this issue.

Ah, the tag on this issue made me remember that the Kotlin DSL tooling models still have hardcoded references to service.gradle.org: https://github.com/gradle/gradle/blob/master/platforms/core-configuration/kotlin-dsl/src/main/kotlin/org/gradle/kotlin/dsl/resolver/SourceDistributionProvider.kt#L98 That is highly likely the root cause.

This is a legit issue, but we don't have an ETA for the fix.

So according to @nomis the problem was solved in a recent Windows update. > I had this problem last week but it has now gone away, on Windows 10 (1909,...

I'm a little confused here because the description mentions bits of the Gradle API and the Tooling API as well. I've attempted to create reproducers for both: - a simple...

This is not an issue with the Tooling API, but the way the `jacoco` plugin is implemented. Calling `getJvmArgs()` in a `taskGraph.whenReady` triggers the resolution of the jacocoagent.jar file, which...

Also, note that the test JVM crashing with an initialisation error. ``` 2024-05-09T14:01:41.256+0200 [QUIET] [system.out] Error occurred during initialization of VM 2024-05-09T14:01:41.256+0200 [QUIET] [system.out] agent library failed to init: instrument...

The problem is present for quite a while. I was able to reproduce the problem with the sample project above using Gradle 7.0.

The issue has been fixed in the latest IntelliJ release (2024.1.1). I think the least we should do is to clearly document the side effects of calling `JavaForkOptions.getAllJvmArgs()`. The documentation...

This is not my area of expertise, but my understanding is that some Groovy bits are part of the Gradle API. For example, we still have a few methods taking...