I have an init script to apply a project plugin with `lifecy Gradle Community #community-support

I have an init script to apply a project plugin wi...

Philip W

04/22/2025, 8:01 PM

I have an init script to apply a project plugin with

lifecycle.afterProject

. But the project does not find the plugin this way, but it finds the plugin if I apply it directly in my build.gradle.kts script.

Philip W

04/22/2025, 8:01 PM

Copy code

// init.gradle.kts
settingsEvaluated {
    pluginManagement {
        repositories {
            maven(url = "<https://maven.pkg.github.com/hfhbd/extract-publications>") {
                name = "GitHubPackages"
                credentials(PasswordCredentials::class)
            }
            gradlePluginPortal()
        }
        plugins {
            id("io.github.hfhbd.extract-publications") version "0.0.3"
            id("io.github.hfhbd.extract-publications.root") version "0.0.3"
        }
    }
}

lifecycle.afterProject {
    if (isolated.buildTreePath == ":") {
        if (this == rootProject) {
            pluginManager.apply("io.github.hfhbd.extract-publications.root")
        }

        pluginManager.withPlugin("maven-publish") {
            pluginManager.apply("io.github.hfhbd.extract-publications")
        }
    }
}

Philip W

04/22/2025, 8:02 PM

If I use this initscript, it fails with

Plugin with id 'io.github.hfhbd.extract-publications.root' not found.

Philip W

04/22/2025, 8:03 PM

But when I apply it manually in the root project, it does not fail:

Copy code

// build.gradle.kts
plugins {
    id("io.github.hfhbd.extract-publications.root")
}

Vampire

04/22/2025, 8:42 PM

Well, you nowhere add the plugin to the classpath, so how do you expect it to be found? Having a plugin in the

plugins { ... }

block does add it to the classpath and if not using

apply false

applies it.

Philip W

04/22/2025, 9:39 PM

Thank you! I didn’t think about that. I thought using the plugin and pluginManagement options would be enough. Now I switched back to the buildscript block and it does work as expected.

Vampire

04/23/2025, 6:56 AM

The

pluginManagement { plugins { ... } }

block only defines default versions if the plugin is used in a

plugins { ... }

block later on without a version, but it does not add anything anywhere.

Philip W

04/23/2025, 12:54 PM

Yeah, makes sense. I normally don’t use the plugins block in pluginManagement, but I failed to use the settings plugins block in settingsEvaluated to add the plugin to the settings classpath. That’s why I use the setting’s classpath directly.

Vampire

04/23/2025, 2:03 PM

Yeah, you cannot use

plugins

blocks like that.

plugins

blocks are extracted before the script in question is compiled. This is then used to get these plugins for compiling the build script. Additionally the extracted block is applied to a dummy project to find out which type-safe accessors to generate and also add those to the compile classpath for the script.

3 Views

Open in Slack

Previous Next