Is there an intended way to do dependency injection in a Gradle plugin? Effectively what I want is to define a task, and that task does like interface.method() and then I would like on execution of the task to actually resolve my intended implementation of interface and use that. The reason I want this is so that I can avoid resolving the dependency for my implementation at configuration time. It was obvious that Gradle itself does this, e.g. the ScalaCompiler task doesn't go and resolve zinc dependencies until it needs them, so I read the code for how it achieves that, and I do sort of understand but equally it makes my head spin a bit. Probably with more thought I can identify the actually important steps and cut out some of the indirection. But I think what I want is probably a very common ask, and probably there's a simple mechanism?

Use the Worker API to avoid having to create classloaders yourself. See example here: https://github.com/tbroyer/gradle-j2cl-plugin/blob/main/src/main/kotlin/net/ltgt/gradle/j2cl/tasks/J2clTranspile.kt

Yep, perfect. Thank you very much. I said it last time I was here but this really is the best support group I've ever used.