From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

it can, it's a nuisance not a real error. I'm not certain if it happens outside of an intellij run though, so maybe scan isn't useful... like I think it's a bug in intellij's integration

Oh, right, its `org/jetbrains/plugins/gradle` so then, yes, you should ask JetBrains about it.

Or you just chime in to the existing issue: <https://youtrack.jetbrains.com/issue/IDEA-325846/failure-to-resolve-a-gradle-project-when-creating-a-gradle-initscript>

Or you switch to an included build instead of `buildSrc`.

<https://scans.gradle.com/s/xd2i4ip5zqr2s>

included build? you mean like just another project?

how does that work with the plugins anyways

since the build scan isn't useful I'm going to delete it

&gt; included build? you mean like just another project?
&gt; how does that work with the plugins anyways
"Another project" depends on what you call project, the term is pretty overloaded. :smile:
It is a separate build just like `buildSrc` is a separate build.
One that can still be in the same source respository, for example at `gradle/build-logic` or also mutliple such builds.
This build you then include using composite build feature and then you can use the plugins that are built by them.
<https://docs.gradle.org/current/userguide/composite_builds.html>

ah, a composite, not a subproject, if you include that then the plugin magic should still work? or does it change the magic import stuff... I imagine it would...

Only marginally. In most cases you should not see much difference