kotlinlang #gradle

I shared a proposal to introduce a Kotlin DSL idiomatic API that would be a subset of the current one, in order to reduce the complexity and the huge API surface currently exposed with many ways to do the same thing. That could allow to provide a much better DevXP without breaking Groovy DSL and the Gradle ecosystem. Please vote for https://github.com/gradle/gradle/issues/24154 if you think that makes sense.

Matt Nelson

03/05/2023, 9:06 AM

Have a kotlin multiplatform library I want to publish, but would like consumers to express capabilities when consuming so that they don't get a shit ton of unnecessary transitive dependencies. Something like Rust's

features

expression where consumers opt-in to a feature and the build system handles it. Anyone know how I might best achieve this?

hisham bin awiad

03/05/2023, 9:33 AM

any one can help me with this issue : i updated all activities on manifest to android:exported=true but is still not fixed

Installation failed due to: 'Failed to commit install session 169461024 with command package install-commit 169461024. Error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: Failed parse during installPackageLI: /data/app/vmdl169461024.tmp/base.apk (at Binary XML file line #139): com.common.broadcast.NetworkBroadCastReceiver: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'

nkiesel

03/09/2023, 1:18 AM

I have a pure Kotlin project with a few external dependencies. I thought IntelliJ dependency tool window would allow me to find updates to them. However, while it shows all of them, clicking on the version number drop-down only shows the current version, even if newer stable versions are available. Any idea what I'm doing wrong?

Pablo

03/10/2023, 7:43 AM

Hello, is the correct channel to ask about

Gradle Managed Devices

? I'm having some issues while running the

Espresso

tests

Marcus Cvjeticanin

03/10/2023, 4:27 PM

Hi, I'm trying to prepare my Kotlin project (ofc using Kotlin DSL with Gradel) to publish on Maven Central. However that is not my question. My question is that, if I have some plugins or other general build tool configuration that I want all other subprojects to inherit. Can I in my root build.gradle.kts define it and all other projects will get the same config? In my root, I have settings.gradle.kts:

include ("library-dir")

Will all of the includes get this? Or how can I do this if not? I just want to avoid writing the same config on several places. Follow-up question regarding the publishing part: • Should I have different versions of the libraries of my SDK? I saw that for example Ktor has the same versions for all libraries since they use a variable to define as

$ktor_version

implementation("io.ktor:ktor-client-core:$ktor_version")
implementation("io.ktor:ktor-client-cio:$ktor_version")

Rasmus

03/11/2023, 10:10 AM

I noticed that there's no built in way to copy test resources from one submodule to a submodule that depends on it. What is the recommended way to include this file:

core/src/test/resources/logback-test.xml

? To the relevant build directory of all of these submodules that depend on the core module:

submodule1/build/resources/test
submodule2/build/resources/test
...

Adam S

03/11/2023, 12:47 PM

is there a Kotlin Multiplatform equivalent for the Java Test Fixtures plugin? I want to share test helpers between subprojects, per target platform (so there would be jvmTestFixtures, jsTestFixtures, etc).

PHondogo

03/13/2023, 5:41 AM

Hello! Is it possible to remove common dependency from target of Gradle Kotlin multiplatform project?

Adrian Witaszak

03/14/2023, 3:03 PM

Hi. Is it possible to add multiple sourceSets for android and ios? Currently, i've got android and ios which are used by native apps, and react bridge in separate module. I wonder if I can add android("reactNative") and ios("reactNative") sourceSets to KMM module and keep react native-related stuff in there, like, for example, the React Native bridge?

Adrian Witaszak

03/14/2023, 5:38 PM

When we import other modules, there is an optional configuration in the project. How do i receive this configuration String in other module?

implementation(project(path = ":AnyModule", configuration = null))

CLOVIS

03/14/2023, 9:44 PM

I want to create convention plugins to simplify my build. However, I have projects that use either

kotlin("jvm")

kotlin("js")

kotlin("multiplatform")

. Is it possible to create a convention plugin that configures all of them? I don't want to create one plugin per Kotlin plugin…

CLOVIS

03/16/2023, 6:56 PM

Does anyone know what the Android plugin maven coordinates are? In convention plugins, we're supposed not to use the plugin ID

CLOVIS

03/16/2023, 8:07 PM

I'm getting when applying the Kotlin Multiplatform plugin as well as the Android library plugin…

Could not create an instance of type org.jetbrains.kotlin.gradle.plugin.mpp.KotlinAndroidTarget.
> Could not generate a decorated class for type KotlinAndroidTarget.
   > com/android/build/gradle/api/BaseVariant

The error message doesn't help me at all, where should I look for to fix this?

Humphrey

03/17/2023, 6:22 AM

Is there any example on how to use gradle version catalog toml where the BOM of spring boot is defined as platform so I don’t need to specify any version of the dependencies that is already provided by that BOM? And how do I override/pin just one version let’s say for the H2 database (com.h2databsse) to an older version? And add additional dependencies that are not there in the spring boot BOM?

helpermethod

03/17/2023, 7:29 AM

Hi! When using Kotlin with Gradle, should I define

java.toolchain

kotlin.toolchain

in my

build.gradle.kts

or both? What is the difference between the two?

Gleb Minaev

03/18/2023, 11:11 AM

Is there a way to mark custom Kotlin source set as a "test source set" in IDEA via Gradle? I know that there is a way to mark standard Gradle source set (via

idea { module { testSources.from(<path to the source directory>) } }

). But Kotlin source sets are not standard Gradle source set... (Here is the use case.) I have a project with separate benchmarks source set. (Which is used in kotlinx.benchmark.) And benchmark tasks are marked as test ones. But the source set is not. So I want to "fix" the difference.

CLOVIS

03/18/2023, 1:27 PM

How can I specify a BOM in a multiplatform project?

kotlin {
    jvm()
    android()

    sourceSets {
        val androidMain by getting {
            dependencies {
                implementation(platform(libs.androidx.compose.bom)) // Unresolved reference: platform
                implementation(libs.androidx.compose.material3)
            }
        }
    }
}

Mustafa Ozhan

03/20/2023, 1:31 PM

is it possible to reach

libs

from

gradle/libs.versions.toml

in pre-compiled scripts located in

buildScr/src/main/kotlin

breandan

03/21/2023, 4:56 AM

Happy to see that the old Groovy property assignment syntax is now (experimentally) supported! https://docs.gradle.org/8.1-rc-1/release-notes.html#experimental-simple-property-assignment-in-kotlin-dsl-scripts FTR, I reported this issue almost six years ago (proper support for array assignment

property = [...]

depends on collection literals): https://github.com/gradle/kotlin-dsl-samples/issues/324 Also related: https://github.com/gradle/kotlin-dsl-samples/issues/712

Zac Sweers

03/21/2023, 5:07 AM

I kinda think it's an awful idea to try to make kotlin look like groovy. Many of Gradle's papercuts are because of ambiguous groovy syntax leading to unexpected code paths

hfhbd

03/21/2023, 1:36 PM

Is there any good documentation about the kotlin mpp gradle plugin for Gradle plugin authors? How to get the targets, the sourcesets and the tasks per target, ideally all lazy? And btw what's the use-case for creating

ObserableSet

and not using

NamedDomainObjectSet

? 🤔

Tianyu Zhu

03/21/2023, 7:56 PM

I have a Kotlin Multiplatform project that uses Kotlin/JS and Kotlin/JVM. Here's a short version of my

build.gradle.kts

plugins {
  kotlin("multiplatform")
  application
}

application {
  mainClass.set("path.to.my.MainKt")
}

kotlin {
  js()
  jvm()
}

I'd like to use

gradlew run

to run the

path.to.my.MainKt

file, but the

run

task doesn't want to use the runtime classpath in

jvmMain

. How do I fix this problem?

Humphrey

03/22/2023, 4:07 PM

How to add Jacoco plugin to TOML version catalog file Instead of

id("jacoco")

in the plugins section of build.gradle I would like to use

alias(libs.plugins.jacoco)

xxfast

03/23/2023, 10:39 AM

Hi all - i have a kotlin multiplatform project with multiple modules

// module-1 build.gradle.kts
plugin {
  kotlin("multiplatform")
}

// module-2 build.gradle.kts
plugin {
  kotlin("jvm")
}

// module-3 build.gradle.kts
plugin {
  kotlin("js")
}

how do I enable

explicitApi

mode for

allprojects{}

of the root build.gradle.pks ?

// root build.gradle.kts
allprojects {
  extensions.configure<KotlinMultiplatformExtension> { explicitApi() } // Extension of type 'KotlinMultiplatformExtension' does not exist. 
}

Nigel Smith

03/27/2023, 9:47 AM

Investigating moving a large-ish multi-project monorepo from maven to Gradle -

gradle init

tries to convert but seems to miss the Kotlin plugin; picks up on some Java (mostly generated via Jooq) and creates only a

java-conventions

file (so never actually tries to compile any of the kotlin) - does anyone know what that tool looks for to pick up on Kotlin in the pom?

dave08

03/28/2023, 7:50 AM

Hi! I just updated a bunch of dependencies (and gradle from 7.1 to 8.0.2) on an older project and got this very cryptic error (posted in thread), googling didn't get any really helpful results...

Alexandre Brown

03/28/2023, 7:27 PM

Hello, we have a Kotlin project with a lot of modules (see image). I am looking for recommendation on how to structure it following the latest gradle recommendation (did not look into gradle for a while). We are currently using Gradle Kotlin 7.1 and the following dsl to apply common dependencies to submodules: backend:build.gradle.kts

subprojects {
    apply(plugin = "org.jetbrains.kotlin.jvm")
	apply(plugin = "com.google.devtools.ksp")

	repositories {
		maven(url = "<https://repo.osgeo.org/repository/release/>")
		mavenCentral()
	}

    ...

    dependencies {
		implementation(project(":core:core-logging"))
		implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:$kotlinxCoroutinesVersion")
        ...
}

I have heard that using this approach is not recommended and that one should use

buildSrc

instead. I also use

gradle.properties

to write the dependencies version : eg

kotlinxCoroutinesVersion=1.6.4

but I am not sure if this is the recommended approach. For Plugins I have the following in the root module (eg:

backend:build.gradle.kts

plugins {
	kotlin("jvm") version "1.7.21" apply false
	kotlin("plugin.serialization") version "1.7.21" apply false
	id("com.google.devtools.ksp") version "1.7.21-1.0.8" apply false
}

Then in the module that needs it I do the following : eg:

backend:backend-frameworks:build.gradle.kts

subprojects {

	apply(plugin = "org.jetbrains.kotlin.plugin.serialization")

	dependencies {
        ...

I would love some feedback and some pointers on how I should structure the dependencies using gradle recommended approach. Some bullet points could help : eg: To share dependencies use ABC, to version dependencies use XYZ. I'm pretty sure the way I set it up is not the recommended approach nowadays and I'm willing to change it.

Title

Alexandre Brown

03/28/2023, 7:27 PM

subprojects {
    apply(plugin = "org.jetbrains.kotlin.jvm")
	apply(plugin = "com.google.devtools.ksp")

	repositories {
		maven(url = "<https://repo.osgeo.org/repository/release/>")
		mavenCentral()
	}

    ...

    dependencies {
		implementation(project(":core:core-logging"))
		implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:$kotlinxCoroutinesVersion")
        ...
}

I have heard that using this approach is not recommended and that one should use

buildSrc

instead. I also use

gradle.properties

to write the dependencies version : eg

kotlinxCoroutinesVersion=1.6.4

but I am not sure if this is the recommended approach. For Plugins I have the following in the root module (eg:

backend:build.gradle.kts

plugins {
	kotlin("jvm") version "1.7.21" apply false
	kotlin("plugin.serialization") version "1.7.21" apply false
	id("com.google.devtools.ksp") version "1.7.21-1.0.8" apply false
}

Then in the module that needs it I do the following : eg:

backend:backend-frameworks:build.gradle.kts

subprojects {

	apply(plugin = "org.jetbrains.kotlin.plugin.serialization")

	dependencies {
        ...

Vampire

03/28/2023, 8:24 PM

I am looking for recommendation on how to structure it following the latest gradle recommendation (did not look into gradle for a while).

https://github.com/jjohannes/idiomatic-gradle

I have heard that using this approach is not recommended

Exact, practically any usage of

allprojects { ... }

subprojects { ... }

is bad and instead convention plugins should be used. Whether you write them in

buildSrc

or an included build or a standalone build that you publish doesn't matter and is totally up to you. I personally prefer an included build, or multiple.

I also use
gradle.properties
to write the dependencies version : eg
kotlinxCoroutinesVersion=1.6.4
but I am not sure if this is the recommended approach.

Nope, the recommended approach is using a version catalog: https://docs.gradle.org/current/userguide/platforms.html

Then in the module that needs it I do the following :

Well, again - and here even more as it is in an intermediate project -

subprojects { ... }

is bad as it introduces project coupling and so prevents more sophisticated features like configure-on-demand or parallel configuration, besides that it makes builds harder to understand and harder to maintain. And also requires to use the legacy way of applying plugins

apply(...)

instead of using the recommended

plugins {... }

block.

Alexandre Brown

03/28/2023, 8:26 PM

Thank you so much @Vampire, I will look at all the links you provided, that's exactly the kind of infromation I was looking for!

Vampire

03/28/2023, 8:31 PM

Also make sure to only use task-configuration avoidance compatible API. So for example no

task("...")

, no

tasks.withType<...> { ... }

, no

tasks.getByName(...)

, only very conservative

tasks....matching { ... }

if at all, no

tasks.create

, ... https://docs.gradle.org/current/userguide/task_configuration_avoidance.html

Alexandre Brown

03/28/2023, 8:32 PM

In some cases I have to use it (eg: third party flag to enable):

extensions.getByType<KspExtension>().apply {
		arg("mockative.stubsUnitByDefault", "true")
	}

But I will try to minimize such cases, thanks!

Vampire

03/28/2023, 10:14 PM

What is that against?

Besides that I would write it simply as

configure<KspExtension> {
    arg("mockative.stubsUnitByDefault", "true")
}

(yes, without

extensions.

)

If you confused that with

tasks.withType

withType

getByType

. And also while you can follow the same rules for all containers (always using

bla.register

, not

bla.create

and so on, it is currently mostly relevant for task collections. As far as I know no other collection is really used lazily yet, so while more future proof, it is not tragic if you don't follow the rules on them. And besides that,

tasks.withType<...>().configureEach { ... }

is fine, that is lazy. But

tasks.withType<...> { ... }

is bad as it would always realize and configure all tasks of that type whether needed or not. (don't ask why, this is because the bad API was there before the task configuration avoidance approach, so it cannot change its meaning easily)

View count: 1