In my KMP

sourceSets

I have the following:

androidMain {
  dependencies {
    implementation(platform(libs.composeAndroid.bom)) // composeAndroid-bom = "dev.chrisbanes.compose:compose-bom:2023.09.00-alpha03"
    implementation(libs.composeAndroid.material3) // composeAndroid-material3 = { module = "androidx.compose.material3:material3" }
  }
}

but I get an error

Cannot convert the provided notation to an object of type Dependency: map(valueof(DependencyValueSource)).

If I move it to a top level

dependencies

block (which the Android plugin uses) it works fine.

Can you explain what this means?

Project accessors enabled, but root project name not explicitly set for 'buildSrc'. Checking out the project in different folders will impact the generated code and implicitly the buildscript classpath, breaking caching.

I have a

buildSrc

project in my multi-project build but

rootProject.name

is set to the "real" root project, not

buildSrc

...

I would like to use a more recent Kotlin version in my "precompiled script plugins" than Gradle's embedded Kotlin version. I use Gradle 8.3 which embeds Kotlin 1.9.0 but in my projects I would like to use Kotlin 1.9.10. Is the following

buildSrc/build.gradle.kts

segment correct in this case?

plugins {
    `kotlin-dsl`
}

...

dependencies {
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.10")
}

Won't this interfere with Gradle's embedded Kotlin 1.9.0? Thanks.

Execution failed for task ':foo:bar:testDebugUnitTest'.
> Process 'Gradle Test Executor 260' finished with non-zero exit value 134
  This problem might be caused by incorrect test process configuration.
  For more on test execution, please refer to <https://docs.gradle.org/8.3/userguide/java_testing.html#sec:test_execution> in the Gradle documentation.

anyone have a clue what is this about? (IDE restart fixes it) is it maybe related to in memory sqlite im using in tests?

I’m trying to run a simple bash script (I’ve run chmod +x on the file) via gradle:

#!/bin/bash
echo "> Yay!"

task:

tasks.register<Exec>("runBashScript") {
    commandLine("./script.sh")
}

But I’m always getting:

Execution failed for task ':runBashScript'.
> A problem occurred starting process 'command './script.sh''

I’m lost 😕

How can I shadow and relocate reflect correctly? I tried relocating the kotlin to kotlin1910. But makes kotlin reflect can't find

kotlin1910.kotlin1910_builtins

. Then, I added custom transformers for avoiding

shadow

relocate the

.kotlin_builtins

constant in kotlin reflect. And relocate the

kotlin/kotlin.kotlin_builtins

to

kotlin1910/kotlin1910.kotlin_builtins

But the reflect can't find the builtin class

AssertionError: Built-in class kotlin1910.Any is not found

Can I include the same project into two included builds (in a complex Kotlin Multiplatform project) and use this setup in Idea? Something like:

root
|- shared
|- project1
|- project2

and

// in root's settings.gradle.kts

includeBuild("shared")
includeBuild("project1")
includeBuild("project2")

// in project1's settings.gradle.kts

includeBuild("../shared")

// in project2's settings.gradle.kts

includeBuild("../shared")

Thanks.

I have a complex multi-module Kotlin multi-platform project. It has a

buildSrc

module loading several common Gradle plugins, used by precompiled script plugins:

// buildSrc/build.gradle.kts

dependencies {
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.10")
    ...
}

The project had no Android support, but now I'd like add the Android plugin as well to one of the sub-modules. It seems that I have to add it to

buildSrc

as well, otherwise I get the error (which seems to be a Gradle classloading conflict):

Unable to load class 'com.android.build.gradle.api.BaseVariant'.

So I added it to

buildSrc

as well:

// buildSrc/build.gradle.kts

dependencies {
    implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.10")
    ...
    implementation("com.android.tools.build:gradle:8.1.1")
}

Gradle sync now works in Idea but when I try to compile the project, errors like the following appear:

Cannot locate tasks that match ':kotlinw:kotlinw-remoting-client-ktor:compileJava' as task 'compileJava' not found in project ':kotlinw:kotlinw-remoting-client-ktor'.

Which I don't understand because the given project is a Kotlin-only project, it has no Java sources, and the Android plugin is not applied to it... Do you have any idea what is happening? Thanks.

dependsOn in kotlinSourceSet (multiplatform) now throw an error in 1.9.20-Beta:

e: commonMain can't declare dependsOn on other source sets

I've got this code:

sourceSets {
        val commonAntlr by creating {
            dependencies {
                implementation(kotlin("stdlib"))
                // add antlr-kotlin-runtime otherwise, the generated sources will not compile
                implementation(project(":3rdparty:antlr-kotlin:antlr-kotlin-runtime"))
            }

            // you have to add the generated sources the to the kotlin compiler source directory list
            // this is not required if you use src/commonAntlr/kotlin and want to add the generated sources to version control
            kotlin.srcDir("build/generated-src/commonAntlr/kotlin")
        }

        val commonMain by getting {
            dependsOn(commonAntlr)

            kotlin.srcDir("build/generated-src/commonMain/kotlin")

            dependencies {
                ....
            }
        }
    }

How to migrate this?

Updating to

1.9.20-Beta

, I'm hit with:

w: Kotlin Source Set 'jvmJavaCodegen' can't depend on 'commonTest' as they are from different Source Set Trees.
Please remove this dependency edge.

Is there somewhere I can learn about Source Set Trees? What constitutes a Tree?

Also looks like the

1.9.20-Beta

plugin marker did not make it to MavenCentral ?

kotlin-gradle-plugin

is there but not the plugin marker?

The Kotlin 1.9.20 Beta blog post mentions that

If you want to have additional source sets that the default hierarchy template doesn't provide...configuring additional source sets manually as usual with dependsOn()

Does that mean that the API for extending the default hierarchy is being removed, or is it not mentioned because it's still experimental?

Is it possible to find unused libs in a

libs.versions.toml

somehow?

Is it possible to register a test task for each target of a KMP project that won't get run as part of build or check (because it's included in allTests)?

Does anyone know if there's a good way to detect what version of the kotlin gradle plugin is applied? I have a plugin where in the past we had a few directories that we were adding to the java sourceset. However, adding to just the java sourceset caused issues when we switched to gradle 8 because we started to get implicit task dependency errors on a few kotlin specific tasks. So I updated the plugin so that it now grabs the kotlinExtension and adds directly to the kotlin sourceset. After making the change, I found out this logic was broken before kotlin 1.9.0. I'm wondering if there's a good way to detect the version so I can just add to the java source set if they are pre kotlin 1.9.0 and add to the kotlin sourceset if they are on or after 1.9.0.

Is there any practical reason for the syntax

webpackTask(
    Action {
        ...
    }
)

instead of the (now deprecated) simpler, more readable, shorter, less verbose, ... :)

webpackTask { 
    ...                
}

Thanks.

Hey I was wondering if it was possible to have a custom version in the

plugins

section.

val test_version: String by project
plugins {
  id("random.plugin") version "$test_version"
}

I want to just have a single value to update that will update the version of a plugin in my entire project. The current error being thrown is

'val test_version: String' can't be called in this context by implicit receiver. Use the explicit one if necessary

Is it possible to remove the

src

sourceset. I tried doing

sourceSets {
    remove(sourceSets.getByName("main"))
}

With no luck

if using a gradle.properties file to specify versions, what's the best way to check for available updates? Android studio has a nice version bump suggestion feature, but it doesn't work when using variables for library versions

Hej, As I understand it KMP used yarn, under the hood, to install dependencies? If so, it is possible to pass arguments? I need to increase the timeout. 🙂 Thanks

Hi, From a custom gradle plugin, I’m reacting to the kotlin plugin being applied,

pluginManager.withPlugin("org.jetbrains.kotlin.jvm")

and trying to configure the the

KotlinCompile

task

tasks.withType<KotlinCompile>().configureEach

. however, gradle says the class can’t be found. This is a JVM project. Any idea why?

I'm trying to create a Plugin that configures sonar and creates all the necessary tasks. Until now all was done inside .gradle scripts, however we want to make use of the type safety of Gradle Plugins. No when I import

import org.sonarqube.gradle.SonarExtension

gradle is not able to resolve the class. (

Unresolved reference: sonarqube

) It clearly is there as the package

org.sonarqube.gradle

can be inspected and contains the File

SonarExtension

. Adding the sonarqube plugin in the build.gradle.kts of the plugin project changes nothing. Does anyone have any experience/hints regarding that matter? Thanks in advance.

Can the new

KotlinTargetHierarchyDsl

be used to implement this in a clean way? In addition to main and test, for all native leaf targets and all nodes shared among them, I’d like to have a

<name>Debug

and

<name>Release

source sets. Later I can create compilations that use these sets as default source set, and configure the binaries depending on

NativeBuildType

. Kind of like this: https://github.com/ilmat192/kotlin-native-gradle-samples/blob/master/debug-logger/build.gradle.kts

Cross posting it here, as I think it's related to Gradle as well 🙏

Hi! Is this the right place to look https://docs.gradle.org/current/userguide/multi_project_builds.html to setup an modular monolith ?

Hello Everyone. we are using app dynamics in our app,

implementation("com.appdynamics:appdynamics-runtime:23.4.1")

after adding app dynamic will cause the very high build times. even we are using M2 pro system also we are added some code to optimise the build times but still not resolved. I request someone to help us, if he/she had experience the same issue and how to fix or reduce build time. see thread i attached some screen ..

Hi, has anyone seen this error message before?

error message: java.lang.NoClassDefFoundError: org.jetbrains.kotlin.resolve.calls.smartcasts.DataFlowInfo (initialization failure)
        at java.base/java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:156)
        at org.jetbrains.kotlin.resolve.LazyTopDownAnalyzer.analyzeDeclarations$default(LazyTopDownAnalyzer.kt:61)
        at org.jetbrains.kotlin.cli.jvm.compiler.TopDownAnalyzerFacadeForJVM.analyzeFilesWithJavaIntegration(TopDownAnalyzerFacadeForJVM.kt:119)
        ...
Caused by: java.lang.NoClassDefFoundError: javaslang.λ
        at java.base/java.lang.ClassLoader.defineClassImpl(Native Method)
        ...
Caused by: java.lang.ClassNotFoundException: javaslang.λ
        at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:827)
        at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
        at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:1095)
        ... 74 more

I've seen it on a MacOS running Gradle 7.2 and 8.3, it happens when compiling

buildSrc

. After deleting

~/.gradle

, the project works well, so I don't really have anything to reproduce with to create an issue. If there is already an issue somewhere, maybe I can add some information to it?

I have created a plugin for doing all the configuration of our android builds. Now the request came from some devs that they would like to have a config file in the root to configure a default for all the project. The structure looks the following:

/
/gradlePlugins <-- In here plugins are specified
/subProjectA
/subProjectB
/build.gradle.kts <-- should apply the plugin to all subprojects and should apply the default config
/settings.gradle.kts <-- here the plugin is included
/default-config.gradle.kts

The defualt-config.gradle.kts should look something like this:

apply(plugin = "my-plugin")

myPluginConfig {
  foo="bar"
}

The build.gradle.kts should include this config something like this:

...
subprojects {
  apply(from = "default-config.gradle.kts")
}

Unfortunately this doesn't work. 1. Because i cannot apply the plugin in the

subprojects

container due to

Cannot run Project.afterEvaluate(Action) when the project is already evaluated.

2. The

default-config.gradle.kts

cannot resolve

myPluginConfig

as well as any imports of it. I have tried countless different scenarios without any luck. Does anyone have an idea on how to do that?

Hi, I am using an

includedBuild

to develop a

kotlin compiler plugin

. The subplugin however is ways being “fetched” and not using the artifact from the included build, which is requiring me to publish to mavenlocal or another repo for testing. Is there a way to have the kotlin compiler use the artifact from the build?