but from within a settings plugin

i see i can do this:

target.gradle.rootProject{
            plugins {
                kotlin("jvm").version("").apply(false)
            }
        }

but that

plugins

call is marked deprecated

it also generates this error:

Using 'plugins(PluginDependenciesSpec.() -> Unit): Nothing' is an error. The plugins {} block must not be used here. If you need to apply a plugin imperatively, please use apply<PluginType>() or apply(plugin = "id") instead.

i tried

target.gradle.beforeSettings {
            pluginManagement {
                plugins {
                    id("org.jetbrains.kotlin.jvm").version("1.9.20")
                }
            }
        }

then

target.gradle.beforeProject {
               plugins.apply("org.jetbrains.kotlin.jvm")
 }

and got

> Plugin with id 'org.jetbrains.kotlin.jvm' not found.

Just add the plugin to the classpath of the settings script, for example with "apply false" in the plugins block (not inside plugin management). The settings script class loader is a parent of the build script class loader

Then you should be able to apply it by only using the id as it then is available in the class loader already

That it is not a settings plugin is irrelevant as you do not try to apply it

but as for adding the plugin to the classpath of settings

i dont see how to do that from a setting plugin...

runtimeOnly

for example if you do not use the classes otherwise

there is just no way to invoke

plugins { }

from a settings plugin apparently?

Then add the plugin to the buildscript configuration

classpath

just like before the

plugins { ... }

block

That should work I think

and that did not work

tried

target.gradle.settingsEvaluated {
            target.gradle.rootProject.buildscript {
                dependencies {
                    classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:"+extension.kotlinVersion.get())
                }
            }

and got

The root project is not yet available for build.

ok this worked:

target.gradle.rootProject {
            buildscript {
                repositories {
                    mavenCentral()
                }
                dependencies {
                    classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:"+extension.kotlinVersion.get())
                }
            }
        }

thanks everyone for your help

I think there is still a functionality gap here though. If i have an initscript/settings plugin that sets up pluginManagement for a bunch of plugins, there is no way to also have a convention plugin (settings or project) that tells projects to apply a plugin by ID, using whichever version was declared in the pluginManagement

I do this in my

KotlinConvention

:

class KotlinConvention : Plugin<Project> {
  override fun apply(target: Project) {
    with(target) {
      with(pluginManager) {
        apply("org.jetbrains.kotlin.jvm")
        apply("org.jetbrains.kotlinx.kover")
        apply("com.squareup.sort-dependencies")
      }
      // configure other stuff
    }
  }
}

e.g. this in your

settings.gradle.kts

?

plugins {
  id("org.jetbrains.kotlin.jvm") version "1.9.22" apply false
}

In my case, the "user" is an init script in a custom distribution

in that case you don't even need to specify a version in

pluginManagement

whatever you put in

classpath

will become the version

If i could start over, my custom wrapper init script would only manage my settings plugins, which are convention plugins, and they would depend on the other plugins

Yeah I was just hoping to invoke the plugins{} closure on a project from a settings plugin