Suhas
04/07/2025, 5:03 PMOleg Nenashev
04/08/2025, 7:56 AMOleg Nenashev
04/08/2025, 7:56 AMRohit Verma
04/08/2025, 12:16 PMcompose.uiTest
or compose.desktop.currentOs
.
Any ideas how to do that??
commonTest.dependencies {
@OptIn(ExperimentalComposeLibrary::class)
implementation(compose.uiTest)
}
desktopTest.dependencies {
implementation(compose.desktop.currentOs)
}
Nitesh Singh
04/10/2025, 9:34 AMBen Dowden
04/13/2025, 6:50 PMimplementation(files("libs/slf4j-android-1.6.1-rc1.jar"))
that I want to exclude from configuration.testImplementation { exclude("org.slf4j"}
but it doesn't seem to work. mockk is complaining that Log.i
isn't a mock objectprudhvi reddy
04/14/2025, 7:11 AMVivek Modi
04/15/2025, 6:28 PMlibs.versions.toml
version catalog in the build-logic:convention
module.Umesh Solanki
04/16/2025, 8:19 AMplugins -> kotlin("multiplatform") version "2.1.20"
kotlin {
jvm {
binaries {
executable {
}
}
}
js(IR) {
binaries.executable()
browser {
commonWebpackConfig {}
}
}
.....
e: 'java' Gradle plugin is not compatible with 'org.jetbrains.kotlin.multiplatform' plugin.
Consider adding a new subproject with 'java' plugin where the KMP project is added as a dependency.
e: 'application' (also applies 'java' plugin) Gradle plugin is not compatible with 'org.jetbrains.kotlin.multiplatform' plugin.
Consider the new KMP/JVM binaries DSL as a replacement: https://kotl.in/jvm-binaries-dslmbonnin
04/18/2025, 4:21 PM#kotlin-gradle-plugin
? https://kotlinlang.slack.com/archives/C0B8W32VA/p1744993229858679Slackbot
04/19/2025, 12:29 PMPHondogo
04/21/2025, 8:23 PMDetected a @Composable function that overrides an open function compiled with older compiler that is known to crash at runtime. Consider recompiling the dependency with a newer compiler version (>= 2.1.20) to get correct behavior
But these 2 modules (dependent and dependency) are compiled with the same version of Kotlin Compose compiler 2.2.0-Beta1
I've made the small reproducer for this warning: https://github.com/hondogo/CustomKotlinCompilerPluginFailureRepro/tree/compose-version-warning
I'd appreciate any help, thanks!Rohit Verma
04/24/2025, 9:01 AMcompose.uiTest
dependency. I added this dependency in the ui-testing
module like this. But it has no effect on the module(home) where I implemented ui-testing
module. However, it works when I defined below dependency directly in the home module. Could anyone please help me with this?
commonTest.dependencies {
@OptIn(ExperimentalComposeLibrary::class)
api(compose.uiTest)
}
Oleg Nenashev
04/24/2025, 2:34 PMZhang Zihan
04/26/2025, 6:51 AMcom.android.kotlin.multiplatform.library
incompatible with applyDefaultHierarchyTemplate
? I used the following code:
kotlin {
@OptIn(ExperimentalKotlinGradlePluginApi::class)
applyDefaultHierarchyTemplate {
common {
group("java") {
withAndroidTarget()
withJvm()
}
}
}
}
But it doesn't seem to work, androidMain
is not successfully included in javaMain
. I can't import the dependencies added to javaMain
in androidMain
.
kotlin {
sourceSets {
getByName("javaMain").dependencies {
implementation(libs.jna.platform)
}
}
}
Edoardo Luppi
04/26/2025, 7:16 PMHexFormat
inside buildSrc
, I get the following error.
Not sure how to actually fix it.unnsse
04/29/2025, 9:55 AM./gradlew test
from the command line...
Using Gradle 8.14
wrote a kts project and whereas it was working before in my macOS based command line:
./gradlew clean test
Reusing configuration cache.
BUILD SUCCESSFUL in 750ms
4 actionable tasks: 4 executed
Configuration cache entry reused.
Am able to run my tests from IntelliJ but this is all it does?martmists
04/29/2025, 11:12 AMCarter
04/29/2025, 12:33 PMjarTask
) although I wanted to see if someone else has explored this.
I’ve got a working series of custom tasks for building a fat jar, then a proguard jar from the fat jar, and was curious if this new DSL could simplify things down.Carter
04/30/2025, 9:53 AMRohit Verma
04/30/2025, 2:08 PMtesting
and add some dependencies in the commonMain
source set:
commonMain.dependencies {
@OptIn(ExperimentalComposeLibrary::class)
api(compose.uiTest)
}
desktopMain.dependencies {
api(compose.desktop.currentOs)
}
And implements this module into another module, i.e., home
module in the commonTest
source set:
commonTest.dependencies {
implementation(projects.uiTesting)
}
Will the dependencies added in the commonMain
inside testing
module included into the build-artifact/APK?blakelee
04/30/2025, 5:32 PMkotlin {
sourceSets {
commonMain.dependencies { }
}
}
However in Kotlin 2.1.20 (Multiplatform) it shows this lint warning under the dependencies
text
> Suspicious receiver type; this does not apply to the current receiver of type NamedDomainObjectContainer. This will apply to a receiver of type NamedDomainObjectProvider, found in one of the enclosing lambdas. Make sure it’s declared in the right place in the file.
What should be the approach here instead? It seems like the documentation should be updatedRohit Verma
05/01/2025, 2:41 PMapi
instead of implementation
When we define some test-dependency for a module, eg - testing
, like this:
commonTest.dependencies {
api(compose.uiTest)
}
Then we cannot access that dependency in a module where I'm implementing testing
module. However, using api should make the dependency transitive but it didn't. Is it a bug or a feature? Because I can easily access the dependency if I define it inside commonMain
source-set using api
.
Please let me know if anyone face this issue and how to deal with it. Thanks :)Edoardo Luppi
05/02/2025, 6:32 PMVampire
05/04/2025, 9:35 PMyarn.downloadBaseUrl = null
got deprecated in KGP 2.1.
It instructs to use yarn.downloadBaseUrlProperty
instead, but that is internal.
😕dead.fish
05/05/2025, 3:11 PMjava.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.incremental.IncrementalCompilationFeatures.<init>(boolean, boolean, boolean, boolean, boolean, int, kotlin.jvm.internal.DefaultConstructorMarker)'
at org.jetbrains.kotlin.gradle.tasks.AbstractKotlinCompile.makeIncrementalCompilationFeatures(AbstractKotlinCompile.kt:288)
at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.makeIncrementalCompilationFeatures(KotlinCompile.kt:476)
at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.callCompilerAsync$kotlin_gradle_plugin_common(KotlinCompile.kt:331)
at org.jetbrains.kotlin.gradle.tasks.KotlinCompile.callCompilerAsync$kotlin_gradle_plugin_common(KotlinCompile.kt:55)
at org.jetbrains.kotlin.gradle.tasks.AbstractKotlinCompile.executeImpl(AbstractKotlinCompile.kt:314)
at org.jetbrains.kotlin.gradle.tasks.AbstractKotlinCompile.execute(AbstractKotlinCompile.kt:263)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:125)
at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:45)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.execute(IncrementalTaskAction.java:26)
at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:244)
Anybody has seen this before?
Thread in Slack ConversationElena van Engelen
05/06/2025, 9:52 AMJacob Kwitkoski
05/08/2025, 6:27 PM1.9.24
due to some internal dependency limitations.
Question: If I include a 3rd-party dependency that upgrades org.jetbrains.kotlin:kotlin-stdlib
to 2.0.21
(as can be seen by running ./gradlew :app:dependencies --configuration releaseRuntimeClasspath
) , is that going to cause problems at either compile time or runtime?loke
05/09/2025, 2:27 PM--add-opens
argument. As such, I have a few questions about this:
• How can I add this JVM argument to the tests in this module?
• Is there a way to get the module to add this parameter to some global list of arguments so all other modules that depend on this one doesn't have to explicitly add this argument to their JVM arguments?Youssef Shoaib [MOD]
05/10/2025, 3:11 PMimplementation(project(":foo"))
doesn't seem to work. Any tips?