Is there any best practises to share jacoco configuration between subprojects via kotlin gradle script?

I had to add all my custom kotlin gradle plugin tasks inside the

project.afterEvaluate

closure due to how it depends on some subprojects being fully evaluated. How do you get the

org.gradle.testfixtures.ProjectBuilder

to force that evaluation? After adding that closure I can no longer see those tasks in my unit tests.

Anyone ever deployed to Heroku with a build.gradle.kts file and without gradlew? I get this error when pushing to heroku

Could not find a 'gradlew' script or a 'build.gradle' file! Please check that they exist and are commited to Git.

which is correct, because I use

build.gradle.kts

(with .kts). This is also in the documentation (https://devcenter.heroku.com/articles/deploying-gradle-apps-on-heroku) but that would mean I HAVE to use

gradlew

instead of the wrapper task in gradle?

how can I add dependencies (using Kotlin DSL) to a custom sourceSet? for example, here are my sourceSets:

sourceSets {
    main {
        java.srcDir("main")
    }
    test {
        java.srcDir("test")
    }
    create("jmh") {
        java.srcDir("jmh")
    }
}

and the problem is that inside the "jmh" sourceSet I can't import my main classes...

I have this plugins block in my build.gradle.kts for my KMP module:

plugins {
    id("com.android.library")
    kotlin("multiplatform")
    kotlin("native.cocoapods")
    kotlin("plugin.serialization") version "1.4.30"
    id("com.chromaticnoise.multiplatform-swiftpackage") version "2.0.3"
}

which gives me this error in AS:

Error resolving plugin [id: 'org.jetbrains.kotlin.plugin.serialization', version: '1.4.30']
> Plugin request for plugin already on the classpath must not include a version

it works if I remove the version, but then fails when I do the iOS framework build. The serialzation github page shows to include the version. What is the issue here?

is there a way to do something like this for all modules in a multiplatform project?

// ignore these warnings
kotlin.target.compilations.all {
    allKotlinSourceSets.forEach { sourceSet ->
        sourceSet.languageSettings.apply {
            useExperimentalAnnotation("kotlinx.coroutines.FlowPreview")
            useExperimentalAnnotation("kotlinx.coroutines.ExperimentalCoroutinesApi")
            useExperimentalAnnotation("io.ktor.util.KtorExperimentalAPI")
        }
    }
}

_What should_ we do _about the current android project?_

UPDATE: To better support the community in this migration, JFrog has extended the JCenter new package versions submission deadline through March 31st 2021. To clarify, the JCenter repository will keep serving packages for 12 months until February 1st 2022. Only the JCenter REST API and UI will be sunsetted on May 1st 2021.

i created backend module in KMM project and to reuse model classes in commonMain source set (shared module), so i just add to ‘backend’ module :

dependencies {
    implementation(project(":shared"))
    ...
}

and i got this error message:

Failed to resolve: project::shared
Affected Modules: KMMM.backend

sorry my english is bad my Repository https://github.com/haitrvnvn/KMMM

More than one file was found with OS independent path 'META-INF/AL2.0'.

Added exclude to the packagingOptions in android{} but still getting err. This is occurring only for instrumented tests. Any ideas?

How could I pass compiler args in a multiplatform repository? e.g. on my root `build.gradle`:

allprojects {
  tasks.withType(org.jetbrains.kotlin.gradle.dsl.KotlinCompile).configureEach { task ->
    task.kotlinOptions {
    }
  }
}

but this errors with

Execution failed for task ':mymodule:runCommonizer'.
> Could not create task ':mymodule:compileKotlinIosArm64'.
   > Cannot query the value of task ':mymodule:compileKotlinIosArm64' property 'compilation' because it has no value available.

note

mymodule

has the

multiplatform

plugin applied

Hey all, I have a multi-module Android project which contains multiple applications. Each one of those application modules includes a set of interfaces that an annotation processor will use to generate code based on the class-path of this module. Today, those interfaces are duplicated, and I can't move them to a shared module due to the code generation requirement (class-path). I tried to create a shared folder and include it as a source directory to all those application modules (I know this sounds ridiculous, but I did not find another way...) but, for some reason, only one of the application modules randomly recognized the folder as part of it (sourceroot) and the others fails (both at IDE and compilation level). Is there a way to include a piece of code in multiple modules to be compiled and processed inside the included module? I appreciate any help you can provide.

Is anyone using

kotlinx.serialization

as part of their Gradle build process? I'vde added the Kotlin Serialization plugin but still classes I've marked

@Serializable

in the script aren't being recognised as such; yielding

kotlinx.serialization.SerializationException: Serializer for class 'MyClassName' is not found.

at the point of use. Any tips?

Hello! I am trying to create a demo project using Kotlin that must build and run in an environment without access to the internet. For the project dependencies I have downloaded all the jars and placed them in a lib directory. I tried doing something similar with the plugin and it’s dependencies, but have not found a way to successfully compile my code. During the build I get the following error:

Could not determine the dependencies of task ':compileKotlin'.
> Could not resolve all files for configuration ':kotlinCompilerClasspath'.
   > Cannot resolve external dependency org.jetbrains.kotlin:kotlin-compiler-embeddable:1.4.10 because no repositories are defined.
     Required by:
         project :

Here is how I’m trying to load the plugin locally:

buildscript {
    repositories {
        flatDir { dirs("plugins") }
    }
    dependencies {
        classpath(":kotlin-gradle-plugin:1.4.10")
        classpath(":kotlin-gradle-plugin-api:1.4.10")
        classpath(":kotlin-gradle-plugin-model:1.4.10")
        classpath(":kotlin-compiler-embeddable:1.4.10")
        classpath(":kotlin-compiler-runner:1.4.10")
        classpath(":kotlin-daemon-embeddable:1.4.10")
        classpath(":kotlin-daemon-client:1.4.10")
        ...
    }
}

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

Can anyone suggest how I can do what I’m attempting? Thanks in advance.

Not sure if this should go to the Gradle Slack, #intellij, or this is the right place but I'm trying it here first. I have a pretty standard Gradle setup with an

includeBuild

where I have

kotlin { explicitApi() }

in the

build.gradle.kts

file. The problem is that IntelliJ completely ignores this setting and every time I have

public something

IntelliJ complains that this is superfluous.

Is there a way to run a Kotlin Fullstack(JVM+JS) with --continuous mode?

Hi all, I had to update to android gradle plugin

com.android.tools.build:gradle

to

7.0.0-alpha09

to get Jetpack compose running. Now when I run

publishToMavenLocal

, I get the error

* What went wrong:
Execution failed for task ':<library>:generatePomFileForLibraryAarPublication'.
> Could not apply withXml() to generated POM
   > Configuration with name 'compile' not found.

Has anyone else run into this issue?

Is there a gradle 7.0.0 migration guide somewhere?

Hey fellow Kotliners. We (Gradle) are hosting a live 30 minute game show t*omorrow* entitled "_*Android Developer Productivity Engineering at Scale".*_ The panelists are @py, @Ty Smith, Emily and myself. We will be asked questions by our host Rooz and you (the audience_)_ will get to vote on the best answers. Register here to watch for free https://gradle.com/devprodeng-showdown-s1e2/ You can also retweet.

Hi there, I've adopted some of my opensource kotlin projects to publish to maven-central using maven-publish and io.codearte.nexus-staging plugin. However, now I'm stuck migrating my newer bits and pieces that use a build.gradle.kts because I still can't wrap my head around how to translate gradle to gradle-kts. Is there a minimalistic example which I could use as template instead?

Hi, I’m using kotlin-js w/ IR compiler and my kotlin gradle scripts in Intellij Community are all red and not supporting auto complete. The project builds just fine, does anyone have a solution to this? Seems to happen in any of my kotlin-js projects.

Hi everyone, not sure if this is the right channel for this but maybe someone can send me to the correct channel if I am wrong. I have created a Project with two modules server (ktor jvm) and client (js ir compiler browser target). The goal I am trying to achive is to get both modules to build when ever there is a change that requires that specific module to be rebuild and to load these changes into the runnning application if possible. I therefore activated devmode for ktor and enabled autoreload. I then start the ktor application from within intellij and also run

gradle installDist -t

for the server module in an extra task. Serverreloads work greate with this solution but I can't get the client js part to work propally. For the client part I added the following code to my build.gradle.kts inside my server module

tasks.withType<Copy>().named("processResources") {
    dependsOn(":client:browserDistribution")
    from(project(":client").tasks.named("browserDistribution"))
}

The first time I make changes to the client module while

gradle installDist -t

is running the changes get compiled and copied over to the servermodule, but any changes after that don't get copied over, even thougth the build is reran. Am I doing something wrong? Any advice on how to fix this?

It seems that it is really related to the way the kotlin plugin compiles kotlin code and uses the module information.

I’m having a bit of trouble with the gradle shadow plugin

com.github.johnrengelman.shadow

I’m trying to create a fat JAR from various kotlin modules and my attempts to exclude transitive dependencies don’t seem to be working. My output JAR is truly fat at 820mb. I’ve tried doing this, which is what I think I need:

dependencies {
    implementation(project(":brainLib")) {
        transitive = false
    }
}

But I get the error:

Could not determine the dependencies of task ':brainLib:compileKotlinJvm'.
> Could not resolve all dependencies for configuration ':brainLib:jvmCompileClasspath'.
  > Cannot change dependencies of dependency configuration ':brainLib:commonMainApi' after it has been included in dependency resolution.

I also tried this, which is supposed to be like a “keep” rule in proguard, but that didn’t work either. (I think because the huge dependencies are transitive under brainLib).

shadowJar {
    minimize {
        exclude(project(":brainLib"))
    }
}

Are there other suggestions as to what I could try?

My gradle syncs in Android Studio (4.1.2) used to take a few seconds, rarely tens of seconds. The past few days they started taking 2+ minutes. The only thing I changed was that I moved

jCenter

below all of my other repositories. The only thing that gets logged is:

> Task :prepareKotlinBuildScriptModel UP-TO-DATE

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See <https://docs.gradle.org/6.8.3/userguide/command_line_interface.html#sec:command_line_warnings>

BUILD SUCCESSFUL in 2m 33s

I'm using Groovy gradle, and don't have a buildSrc directory. My project uses Kotlin 1.4.31. Anyone know what's up with that?

Hello! I have multi module gradle project with kotlin multiplatform as a module. In one gradle module i created custom common sourceset and in other module i want to depend on them in common code. How can I do this?

Is it possible to limit the amount of kotlin and gradle daemons? I'm working on a mpp library and an android application simulatenously and now I have the double amount of ram consumption. I'm on 32gig ram but that still pushes my system to the limit

hey! does anyone else have the problem that IDEA depends on the gradle-api jar and that dependencies in the that jar conflict with your local classes (in my case f.ex. slf4j which is also packages in the gradle jar)

Anyone else see

java.lang.NoClassDefFoundError: Could not initialize class org.jetbrains.kotlin.com.intellij.pom.java.LanguageLevel

trying to run a Gradle build with Kotlin scripts under

buildSrc

using the new Zulu JDK 16?

Question on compile vs runtime versions. I have an app that has a transitive dependency that shows up on the compile classpath

grpc 1.17

. I depend on another library that uses

implementation grpc 1.32

. So on the runtime classpath it correctly resolves to

|    |         +--- io.grpc:grpc-netty:1.17.1 -> 1.32.2 (*)

. The problem is when you actually run the application you get a noclassdef found error for something that exists in

1.32

. A hack to fix this is for the app to depend on

1.32

itself but I'm trying to understand why this is a problem. The runtime classpath is resolving how I expect it to. Are the compile classpath versions strictly preferred or something?