@Tapchicoma you published an experimental version of a Kotlin ecosystem https://github.com/Kotlin/declarative-gradle-jetbrains-ecosystem-plugin Will it be a experiment or do you accept issues and pull requests?

Please wait until Kotlinconf with issues and PRs. We need to add some more definitions to it and Marcin Mycek will do a 15 min presentation on this topic. After it we are open for feedback and improvements. Also please note that currently

BuildModel

s are not designed at all and mostly skipped. At some point we will probably will do this.

Okay, then I will wait and watch the presentation in two weeks. I am mostly interested in a kotlinJvmLibrary

it is next definition that I will add 🙂

Stupid question, why only library? 👀

if you really want to play with it:

pluginManagement {
    repositories {
        maven {
            url = uri("<https://raw.githubusercontent.com/Kotlin/declarative-gradle-jetbrains-ecosystem-plugin/refs/heads/maven2>")
        }
        mavenCentral()
        gradlePluginPortal()
    }
}

plugins {
    id("org.gradle.toolchains.foojay-resolver-convention").version("1.0.0")
    id("org.jetbrains.ecosystem").version("0.67.0")
}

dependencyResolutionManagement {
    repositories {
        mavenCentral()
    }
}

rootProject.name = "untitled4"

Makes sense, but I would still expect kotlinLibrary, to add the kotlin prefix for a project type because library is a very broad name.

let's discuss it after Kotlinconf - any feedback is welcome. And, probably it would be better to do in Kotlinlang slack, so other colleagues could participate in the discussion

I know I know, you said I should wait, but any change to add

PlatformDependencyModifiers

and

TestFixturesDependencyModifiers

to the Dependencies?

I guess we could accept this - feel free to submit a PR

requested few changes