following on from the message above, I have a versions catalog where I define the dependencies - is ...

# gradle

[Francesc]

following on from the message above, I have a versions catalog where I define the dependencies - is it possible to use that in the buildSrc/build.gradle.kts? Details in thread

[Francesc]

current file

plugins {
    `kotlin-dsl`
    `kotlin-dsl-precompiled-script-plugins`
}

repositories {
    mavenCentral()
    google()
}

dependencies {
    implementation("com.android.tools.build:gradle:7.3.0-alpha07")
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.10")
}

intended solution (doesn't build)

plugins {
    `kotlin-dsl`
    `kotlin-dsl-precompiled-script-plugins`
}

repositories {
    mavenCentral()
    google()
}

dependencies {
    implementation(libs.com.android.tools.build.gradle)
    implementation(libs.org.jetbrains.kotlin.kotlin.gradle.plugin)
}

[ephemient]

https://github.com/gradle/gradle/issues/15383 basically plugins cannot assume that they'll be running in a build with the same version catalog, so you have to use the non-typesafe API

[Francesc]

thanks for the link, I'll look into that workaround

[Vampire]

That answer does not really fit the question, as you try to use the version catalog in the build script of the plugin build, not within the precompiled script plugin. Just define the version catalog with the path to the toml file in the settings script of the plugin build.

[Francesc]

thanks, I tried that, but then libs is not recognized in the build script, this is my settings.gradle.kts in buildSrc

dependencyResolutionManagement {
    versionCatalogs {
        lib {
            from(files("../gradle/libs.versions.toml"))
        }
    }
}

[Vampire]

well, if you define a version catalog called "lib" how can you expect it to be available under the name "libs"? 😉

[Francesc]

yes, sorry, it was a typo, it's called libs everywhere

[Francesc]

this is the build.gradle.kts file

plugins {
    `kotlin-dsl`
    `kotlin-dsl-precompiled-script-plugins`
}

repositories {
    mavenCentral()
    google()
}

dependencies {
    implementation(libs.com.android.tools.build.gradle)
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.10")
    implementation("com.google.dagger:hilt-android-gradle-plugin:2.41")
}

[Vampire]

Why do you try to confuse me? 😞
It does not complain that it does not find libs in the build script.
It complains that it does not find libs in the settings script.

[Vampire]

Replace libs { by create("libs") { and it should work fine

[Francesc]

thanks for your help. That didn't make a difference unfortunately

dependencyResolutionManagement {
    versionCatalogs {
        create("libs") {
            from(files("./../../gradle/libs.versions.toml"))
        }
    }
}

and

plugins {
    `kotlin-dsl`
    `kotlin-dsl-precompiled-script-plugins`
}

repositories {
    mavenCentral()
    google()
}

dependencies {
    implementation(libs.com.android.tools.build.gradle)
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.10")
    implementation("com.google.dagger:hilt-android-gradle-plugin:2.41")
}

libs is not recognized

[Vampire]

Then you need to provide an MCVE, it works fine here

[Francesc]

not an MCVE, but this shows the issue: https://github.com/fvilarino/Weather-Sample/tree/feature/precompiled_plugin

[Vampire]

message has been deleted

[Francesc]

yup, it works when you place things in the right place, thanks, much appreciated!

[Francesc]

aren't we threaded already?

[Vampire]

Sorry, misclicked

[Francesc]

I see the IDE doesn't have support for this though, it shows all red, but it compiles fine

[Vampire]

No, should work fine after you synced

[Vampire]

Only plugins from version catalogs don't work properly iirc

[Vampire]

Or well, sometimes in some places it works, sometimes not. The support is partly still a bit flaky

[Francesc]

after syncing it's still red, but I'm not concerned about this as it works fine