Hi, is there a way to use gradle’s

includeBuild

and

dependencySubstition

to avoid having the kotlin compilation process pull a compiler plugin from a remote repository (like

mavenLocal

) so that we don’t have to publish the

kotlin compiler plugin

before debuggin?

With included builds, AFAIK you just have to make sure that the maven coordinates match and there’s no need to use

dependencySubstitution

explicitly (though you could if needed). I don’t think there’s anything special about how compiler plugins are resolved, your scenario used to work fine for me.

ok, i’ll see if I can find out what might be causing the download then. thanks!

For help, I’d ask in #gradle . To solve on my own, I guess I’d go through the

includeBuild

documentation in Gradle and check what’s wrong.

project.group

,

project.version

and the module name must match the Gradle dependency as added by your gradle plugin

ya they do, i’ll ask there, thanks!

Do an

gw outgoingVariants

on the producer to see what it producers

i ran

./gradlew outgoingVariants

on the build i am including. It says there are none. Did i run the command in the right place? @Vampire

Maybe not? Or maybe it is like dependencies and not runs on all projects in the build, I'm not sure, in the sauna right now. :-)

lol okay

We'll maybe see if you finished the MCVE. :-)

yup

Hea, as I suspected,

gw :buildLogic:plugin-gradle:outgoingVariants

and

gw :buildLogic:plugin-kotlin:outgoingVariants

show the respecting outgoing variants.

so i am ignorant of this, how do we use that information to include the sibling project?

It's just to see the capabilities that are published to see you used the right artifact coordinates. For the include problem I already told you how in the other thread before you even posted the MCVE, you just said it does not work which is not true, at least not in your MCVE 🙂