This message was deleted.

Did you simply try it?

Yes, and it didn't work

An included build is an included build, not an included project. Included projects are part of a multi-project build and can be referenced with

project(...)

. Included builds are own builds and you cannot reference them with

project(...)

, you just reference them by their normal Maven coordinates like any other dependency.

I'm pretty sure I tried both, but thanks for the pointer. I'll give it a try later

Not if your included build is properly set up. Use it's

outgoingVariants

task and you should see the coordinates you need to use.

looks like it's not supported https://github.com/gradle/gradle/issues/12978. I'm getting that same error.

"that same error."? That you cannot use

includeBuild

from

buildSrc

? That is expected. I just thought it might maybe work like with the plugin, that you included from the root build and can access it from

buildSrc

since the order changed and settings are now evaluated before

buildSrc

. This was the other way around in older Gradle versions.

if you're referring to sharing the plugin in

includeBuild

to

buildSrc

, I'm aware that works. The missing piece for me is how to reuse the classes in that plugin as a dependency.

No, I'm not, what you want is exactly what I meant and said

oh i see, the

settings.gradle

for

buildSrc

No, not the settings script of

buildSrc

, you do not listen

it's already included in my rootProject's

settings.gradle

Then you just need to properly declare the dependency as I said multiple times already.

i'm on Gradle 7.3.3

There it should probably work

could you perhaps point to a working example? I'm trying my best and it's not as easy for me as it might be for you 😉

I don't have one, I just wrote it ad-hoc into my play project and it simply worked. But I don't know what to show, it is just the two lines. The

includeBuild

in the parent settings script and the dependency in the

buildSrc

build script with the correct coordinates as can be found as capability in the output of

outgoingVariants

task as already mentioned. There is really nothing more to it.

this is what I have in

settings.gradle

pluginManagement {
    includeBuild ('gradle/gradle-plugin')
}

includeBuild ('gradle/gradle-plugin')

in

gradle/gradle-plugin/settings.gradle

rootProject.name = "plugin"

include(":plugin")
include(":buildtools")

in

buildSrc/build.gradle

, I tried both the maven coordinates and project

If you don't get it running, you should try to produce an [MCVE](https://stackoverflow.com/help/mcve) that shows where you have problems.

ok i'll try to repro in a smaller project and if I can, i'll post to S/O thanks

That does not look like proper coordinates

and seems like this was fixed maybe in Gradle 7.4 https://github.com/gradle/gradle/issues/18984

Ah, quite possible then. As I said, I tried with 7.4.2. Was not aware there was some bug in previous version.

turns out you were right all along but I was hitting errors because i'm on Gradle 7.3.3 and even when upgrading to Gradle 7.4.2, I'm hitting an Idea bug that is fixed here, but that's a beta version of Android Studio (Dolphin). I probably can't use this method until Dolphin goes GA. (because large eng org) Recap as you mentioned

The

includeBuild

in the parent settings script and the dependency in the

buildSrc

build script with the correct coordinates as can be found as capability in the output of

outgoingVariants

task as already mentioned.

Can't you update the Kotlin plugin? It's not fixed in the IDE but in the Kotlin plugin.

oh i see, thanks for pointing that out.. I'll see if that works

It is already on 1.7.0, that's the latest release, what updates do you expect?

it's still not working in that release i screenshotted. I don't know how IJ versioning works, but I'm assuming I need 213 Fixed in • IJ 221.1623 (Kotlin 221-1.5.10-release-955-IJ1623) • IJ 213.6094 (Kotlin 213-1.5.10-release-949-IJ6094)

If it is fixed in 1.5.10, I strongly assume it is fixed in any 1.7.0 version which comes way later