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

Gradle Community

I'd wonder if that is the case.
AS is basically just a customized IJ version.
Well, the base version might be a bit older than your IJ version, but I don't think that should hurt.
Unless you also copied over the metadata (`.idea`).
What actually looks a bit strange is this I'd say:

The weird part is because, my buildSrc/build.gradle.kts adds the src/main/kotlin/base folder to the java sourceSet:
```...
sourceSets.main {
    java {
        srcDir("${projectDir.parent}/src/main/kotlin/base")
        include("Plugins.kt")
        include("Versions.kt")
    }
}```
Someone gave me this advice with the effect, to have my Version constants also available in my project level `build.gradle.kts`

<@URQ797WRW> Thanks for your effort to set up this great example :pray: I will go with the versions catalog. I have set up the build in IntelliJ and it builds successfully. In my android project I try to apply the pre compiled script plugin of my composite build but I get an error. Can you have a look please?

<@URQ797WRW> Now it builds successfully :slightly_smiling_face:
Can you explain me what the `base` plugin is good for and `implementation(files(libs.javaClass.protectionDomain.codeSource.location))` ? Especially the `files` command...

I also noticed that there is a generated `PluginSpecBuilders.kt` file with plugin accessors. I'm wondering why I can't use
```plugins {
    base
    `application` // instead of id("com.android.application")
     `kotlin-android` // instead of id("kotlin-android")
}```
My last question is regarding the screenshot: Why do I have to declare the pluginManagement block. Does it declare the dependencies lookup for the project? I'm wondering why `allprojects.repositories` isn't sufficient :thinking_face: