This message was deleted.

Gradle 7.6 introduces customization in this area.

Nice. Sad that you still cannot create a toolchain from some local path like a JVM the build constructed.

agreed, instead of fixed-sources (Gradle props that specify environment variables or lists of paths), just provide a

searchLocations

property on the toolchain extension.

What I mean is more dynamic. The build produces some JDK that will be shipped with the end product and it should already be used by the tests for example, or by the

run

task. I think I have an open feature request for it somewhere.

I mean, I think if it can download stuff you should be able to provide a URL. Local path would be nice too... Maybe just a URI and if that's file handling appropriately

No, that wouldn't work out. With that mechanics the JDK would be "downloaded" the first time and installed into the auto-provision folder. As long as the major version or another one of the identifying attributes does not change it would be reused and even across projects.

can we have both?

Hopefully