Hi @Goooler, this issue is relevant for my project as well and I feel that I could contribute to fix the issue. But before I start working on PR, I wanted to make sure that implementation idea is viable...

The idea is to:

1. Make FormatExtension.lazyActions aware of Gradle Jvm toolchain configuration.

   • First option is to execute these lazy actions using the Worker API with process isolation and Gradle Jvm toolchain configuration.
   • Alternative option is to iterate upon the defaultVersion() concept and fix it in such a way that the Jvm.Support class would respect Gradle Jvm toolchain configuration instead of simply relying on java.version system property.

2. Migrate SpotlessTaskImpl to execute operations via Worker API (again with process isolation and with respect of toolchain configuration)

@Goooler, please let me know what you think about it and if you have any suggestions.

Looks like this might be a duplicate of #724

@mr-serjey Thanks for your response! I would prefer the second. WDYT? @nedtwigg

Correct, this is a dupe of #724, even though this issue has the better discussion, I'm going to close this one so that watchers of the original issue will get notified if something gets merged.

I don't have a preference for 1 vs 2, so I defer to the implementor and I think @Goooler has good insight that option 2 is probably easier. But I think that migrating the defaultVersion() concept in the Jvm.Support class is non-optional, the user experience will be poor without it.