are convention plugins generally recommended over custom logic applied inside

afterEvaluate {}

? I wonder mostly in terms of correctness and performance

I have a plugin based on this template -> https://github.com/bnorm/kotlin-ir-plugin-template performance is terrible, IDE has issues with providing any support. Even auto-complete works very slowly - (if works, most of the time it does not work). to find issues in my code I need to run gradle build (issues like missing imports). After gradle build and some long wait it can find class that is not imported. Any idea what makes this plugin so bad from a performance point of view?

hey all, I need your help about gradle-build speed, this is build-scan report, I find it not impored after upgrade gradle-7.4.2 & jdk11. or you have more method to impove build speed like okbuck. I have configed according to APG document, it's not good maybe My project is so big. https://scans.gradle.com/s/uvsxvyjhqcwze

This gradle tasks works correctly, I can see the file at the

into

location

tasks.register<Copy>("copyIosTestResources") {
    from("src/commonTest/resources")
    into("build/bin/iosX64/debugTest/resources")
}

tasks.findByName("iosX64Test")!!.dependsOn("copyIosTestResources")

But if I try to do the same for my js target with this

tasks.register<Copy>("copyJsTestResources") {
    from("src/commonTest/resources")
    into("build/js/test/resources")
}

tasks.findByName("jsTest")!!.dependsOn("copyJsTestResources")

I tried a bunch of different values for

into

but it doesn’t seem to work at all. Any idea why?

How could I run the test tasks in all the subprojects hierarchy from the root project (preferrably in a way Intellij could display the results...)?

For some reason it seems to run the tests for only one of the many submodules...:

// in the root build.gradle.kts:
tasks.named<Test>("test") {
    useJUnitPlatform()
    testLogging {
        showExceptions = true
        showStandardStreams = true
        exceptionFormat = FULL
    }
}

How can you add additional dependencies depending on the configuration at the configuration stage with included and substituted modules? Use-case: I want to support configuration cache for licensee. Licensee resolves the dependency pom files and checks its license, so it needs to add a

pom

dependency for each dependency, transitively. At the moment, this is done in the task action, so the pom dependency is added during the task action, but this breaks the configuration cache. I moved the additional pom file dependency to the configuration stage, but now I have a problem with module substitution:

Adding a dependency substitution rule to a configuration changes the timing of when that configuration is resolved.

Is there any workaround possible? https://github.com/cashapp/licensee/pull/141

Hey! I’m trying to apply the Compose Rules plugin to my project, but I’m having some issues. Both my detekt and ktlint configurations are precompiled Gradle scripts in KTS. How could I add a plugin here?

// detekt.gradle.kts
apply<DetektPlugin>()

configure<DetektExtension> {
    config = files("$rootDir/config/filters/detekt.yml")
    allRules = true
}

tasks.withType<Detekt>().configureEach {
    exclude("**/resources/**,**/build/**")
}

Hey! Our Android Project build make some log about R8. Maybe you have meet it(print many times and long time ). need your help to solve it or improve Our project.

WARNING:/Users/alger/.jenkins/object_android_apk_pack_gradle7/VeSync_RN/android/app/build/intermediates/transforms/sensorsAnalyticsAutoTrack/check/releaseStaging/57.jar: R8: Expected stack map table for method with non-linear control flow. In later version of R8, the method may be assumed not reachable.

Hey! Adding

testImplementation

dependency on

Gradle API

triggers a conflict of loggers and blocks further work, since

SLF4J: Class path contains multiple SLF4J bindings.

Is it possible to “cut off” the gradle logger so it won’t be on the classpath? Some context related details: • It’s added just as a dependency

testImplementation(gradleApi())

• The goal of adding Gradle API is for enabling an ability to run some custom gradle tasks during integration/end-to-end testing (I’m using JUnit) • It doesn’t seem possible to exclude the logger as it’s built-in into the Gradle source, so it seems not even a dedicated module that could be possible to just exclude from the build 🤷‍♂️ an error messages:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:$HOME/.gradle/caches/7.5/generated-gradle-jars/gradle-api-7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:$HOME/.gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-classic/1.2.11/4741689214e9d1e8408b206506cbe76d1c6a7d60/logback-classic-1.2.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See <http://www.slf4j.org/codes.html#multiple_bindings> for an explanation.
SLF4J: Actual binding is of type [org.gradle.internal.logging.slf4j.OutputEventListenerBackedLoggerContext]
...
Caused by: java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.gradle.internal.logging.slf4j.OutputEventListenerBackedLoggerContext loaded from file:$HOME/.gradle/caches/7.5/generated-gradle-jars/gradle-api-7.5.jar). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.gradle.internal.logging.slf4j.OutputEventListenerBackedLoggerContext
...

Please suggest what are the options to resolve this conflict which 🙏

gradle build -t

allows you to always automatically build when you make changes is there a way to automatically restart an application after a rebuild? I was trying

gradle run -t

which is running the application, but it doesn't rebuild and restart when making changes.

hi, I'm trying to follow the Gradle guide for writing a custom plugin as a standalone project as described here https://docs.gradle.org/current/userguide/implementing_gradle_plugins.html#plugin-development-plugin code in thread

Anyone seeing this warning?

e: java.rmi.ServerError: Error occurred in server thread; nested exception is:
        java.lang.NoClassDefFoundError: org/jetbrains/kotlin/daemon/common/CompileService$CallResult$Dying
Could not perform incremental compilation: Could not connect to Kotlin compile daemon
Could not connect to kotlin daemon. Using fallback strategy.

Hi, anybody fit in gradle init scripts (init.gradle.kts)? I want to enable the kotlin compiler setting

allWarningsAsErrors

I do not want that in general, just on my local machine (as this would also fire when there are deprecations) Currently my file includes:

allprojects {

  afterEvaluate {
    if (tasks.findByName("compileKotlin") == null) {
      logger.lifecycle("[init.gradle.kts] no kotlin project")
    }
    else {
      logger.lifecycle("[init.gradle.kts] adding 'allWarningsAsErrors = true'")
      tasks.withType<org.jetbrains.kotlin.gradle.tasks.KotlinCompile> {
        kotlinOptions {
          allWarningsAsErrors = true
        }
      }
    }
  }
}

When I run my project it is showing the

[init.gradle.kts] adding 'allWarningsAsErrors = true'

log message, but the warnings do not make the build fail. if I add that flag to the build script, it does fail. Any idea what I am doing wrong?

The Gradle build cache docs recommend only pushing to the remote build cache on CI server builds. Is it desirable to restrict this further to builds of the trunk branch only? Or would it be okay to enable CI server remote build cache pushes for PR branches that have not yet been merged into the trunk branch?

Hi! This is my gradle settings. But when i run

./gradlew shadowJar

, it appears two jars files. One named app.jar and another named sokos-ktor-template.jar. Why do i get two jars ?

import com.github.jengelman.gradle.plugins.shadow.tasks.ShadowJar
import org.gradle.api.tasks.testing.logging.TestExceptionFormat.FULL
import org.jetbrains.kotlin.gradle.tasks.KotlinCompile
import org.openapitools.generator.gradle.plugin.tasks.GenerateTask

val ktorVersion = "2.1.3"
val junitJupiterVersion = "5.9.1"
val logbackVersion = "1.4.4"
val logstashVersion = "7.2"
val jacksonVersion = "2.14.0"
val prometheusVersion = "1.10.0"
val kotlinLoggingVersion = "3.0.4"

plugins {
    kotlin("jvm") version "1.7.21"
    kotlin("plugin.serialization") version "1.7.21"
    id("org.openapi.generator") version "6.2.1"
    id("com.github.johnrengelman.shadow") version "7.1.2"
}

group = "no.nav.sokos.prosjektnavn"
java.sourceCompatibility = JavaVersion.VERSION_17

repositories {
    mavenCentral()
    maven { url = uri("<https://maven.pkg.jetbrains.space/public/p/ktor/eap>") }
}

dependencies {

    // Ktor
    implementation("io.ktor:ktor-server-core-jvm:$ktorVersion")
    implementation("io.ktor:ktor-server-netty-jvm:$ktorVersion")
    implementation("io.ktor:ktor-client-apache:$ktorVersion")
    implementation("io.ktor:ktor-client-content-negotiation:$ktorVersion")
    implementation("io.ktor:ktor-server-metrics-micrometer:$ktorVersion")
    implementation("io.ktor:ktor-server:$ktorVersion")
    implementation("io.ktor:ktor-server-status-pages:$ktorVersion")

    // Jackson
    implementation("io.ktor:ktor-serialization-jackson:$ktorVersion")
    implementation("com.fasterxml.jackson.core:jackson-databind:$jacksonVersion")
    implementation("com.fasterxml.jackson.module:jackson-module-kotlin:$jacksonVersion")
    implementation("com.fasterxml.jackson.datatype:jackson-datatype-jsr310:$jacksonVersion")

    // Monitorering
    implementation("io.micrometer:micrometer-registry-prometheus:$prometheusVersion")

    // Logging
    implementation("ch.qos.logback:logback-core:$logbackVersion")
    implementation("ch.qos.logback:logback-classic:$logbackVersion")
    implementation("net.logstash.logback:logstash-logback-encoder:$logstashVersion")
    implementation("io.github.microutils:kotlin-logging-jvm:$kotlinLoggingVersion")

    // Test
    testImplementation("io.ktor:ktor-server-tests-jvm:$ktorVersion")
    testImplementation("org.junit.jupiter:junit-jupiter-api:$junitJupiterVersion")
    testImplementation("org.junit.jupiter:junit-jupiter-params:$junitJupiterVersion")
    testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:$junitJupiterVersion")
}

sourceSets {
    main {
        java {
            srcDirs("$buildDir/generated/src/main/kotlin")
        }
    }
}

tasks.named<GenerateTask>("openApiGenerate") {
    generatorName.set("kotlin")
    generateModelDocumentation.set(false)
    inputSpec.set("$rootDir/specs/pets.json")
    outputDir.set("$buildDir/generated")
    globalProperties.set(
        mapOf(
            "models" to ""
        )
    )
    configOptions.set(
        mapOf(
            "library" to "jvm-ktor",
            "serializationLibrary" to "jackson"
        )
    )
}

tasks.named<ShadowJar>("shadowJar") {
    archiveFileName.set("app.jar")
    manifest {
        attributes["Main-Class"] = "no.nav.sokos.prosjektnavn.BootstrapKt"
    }
}

tasks.withType<KotlinCompile> {
    dependsOn("openApiGenerate")
    kotlinOptions.jvmTarget = "17"
}

tasks.withType<Test> {
    useJUnitPlatform()
    testLogging {
        exceptionFormat = FULL
        events("passed", "skipped", "failed")
    }

    // For å øke hastigheten på build kan vi benytte disse metodene
    maxParallelForks = Runtime.getRuntime().availableProcessors() / 2
    reports.forEach { report -> report.required.value(false) }
}

Hi, for a project, I need to download some JSONs and generate Kotlin code from these JSONs before building the project, or just at some time using a gradle task, how can I achieve this ? (It's for generating an enum containing all the blocks of Minecraft for a project that I own that let's you generate Minecraft Java DataPacks from Kotlin code, the enum will be there to have better typings when targeting a block instead of just a String)

Anyone affected by upgrading to Gradle 7.6? I'm getting this

Multiple incompatible variants

error: https://pastebin.com/t3tx8SCy. See the PR to reproduce: https://github.com/krzema12/github-workflows-kt/pull/569

Hi! I'm struggling with this error: https://gist.github.com/gabrielleeg1/4368e838f75d1333f7da962abef32933 And the build script for the

buildSrc

file is simply:

plugins {
    `kotlin-dsl`
}

repositories {
    maven("<https://plugins.gradle.org/m2/>")
    mavenCentral()
}

Can anyone help me?

[Edit] ✅ resolved. hello folks, Running into issues with Gradle config..

Required by:
    project : > org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.7.21 > org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.21
Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could not resolve org.jetbrains.kotlin:kotlin-scripting-compiler-impl-embeddable:1.7.21.
Caused by: org.gradle.api.resources.ResourceException: Could not get resource '<https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-scripting-compiler-impl-embeddable/1.7.21/kotlin-scripting-compiler-impl-embeddable-1.7.21.pom>'.

Cert validation is failing for

Caused by: org.gradle.api.resources.ResourceException: Could not get resource '<https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-scripting-compiler-impl-embeddable/1.7.21/kotlin-scripting-compiler-impl-embeddable-1.7.21.pom>'.

Caused by: org.gradle.internal.resource.transport.http.HttpRequestException: Could not GET '<https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-scripting-compiler-impl-embeddable/1.7.21/kotlin-scripting-compiler-impl-embeddable-1.7.21.pom>'.

my config

➜  ~ java -version
openjdk version "17.0.5" 2022-10-18
OpenJDK Runtime Environment Homebrew (build 17.0.5+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.5+0, mixed mode, sharing)
➜  ~ gradle -v

------------------------------------------------------------
Gradle 7.6
------------------------------------------------------------

Build time:   2022-11-25 13:35:10 UTC
Revision:     daece9dbc5b79370cc8e4fd6fe4b2cd400e150a8

Kotlin:       1.7.10
Groovy:       3.0.13
Ant:          Apache Ant(TM) version 1.10.11 compiled on July 10 2021
JVM:          17.0.5 (Homebrew 17.0.5+0)
OS:           Mac OS X 12.6.1 aarch64

➜  ~

I am using

IntelliJ IDEA 2022.2.4 (Community Edition)

Is anyone facing this issue?

Kotest builds with Gradle 7.6 are failing. Anyone seen this problem already? https://github.com/kotest/kotest/pull/3302

* What went wrong:
A problem occurred configuring project ':kotest-framework:kotest-framework-multiplatform-plugin-gradle'.
> Failed to notify project evaluation listener.
   > org.jetbrains.kotlin.gradle.plugin.KotlinGradleSubplugin: Provider org.jetbrains.kotlin.samWithReceiver.gradle.SamWithReceiverGradleSubplugin not a subtype
   > org.jetbrains.kotlin.gradle.plugin.KotlinGradleSubplugin: Provider org.jetbrains.kotlin.samWithReceiver.gradle.SamWithReceiverGradleSubplugin not a subtype

This builds just fine ✅ and IDE references as well ✅, but crashes at runtime ❌ any help will be appreciated ?

How can I enable explicit API mode in Kotlin Multiplatform, using the Gradle DSL?

Those who see variant selection issue on using KotlinGradlePlugin +

kotlin-dsl

plugins after updating to Gradle 7.6 should also add

id("org.jetbrains.kotlin.plugin.sam.with.receiver") version "<kotlin_version>"

into

plugins { .. }

block. Related issue that should be fixed in Kotlin 1.8.20 release.

Hi! For my java projects I can write the following in my Gradle file:

java.targetCompatibility = JavaVersion.1_8

Is there a similar way I can set the

jvmTarget

for my Kotlin code?

I’m trying to update a Kotlin multiplatform project to Kotlin 1.7.21, and I’m hitting a failure that I’m including in a thread. The project is using Gradle 7.6. I use kts for my build scripts, and I have some build conventions set up. Because the build conventions are for the Kotlin multiplatform Gradle plugin, I do include the Kotlin 1.7.21 plugin in the build convention dependencies. The last thing I have is dependency locking enabled. The build failure happens when I trigger a build on GitHub Actions, but I can’t trigger the same failure locally on my Mac. I realize that’s a lot of variables, but I suspect the combination of dependency locking and including Kotlin 1.7.21 for the build convention ends up causing the failure. If I disable dependency locking, the issue goes away. I’m glad to file a YouTrack issue, but I’m having trouble narrowing this down further. Thoughts on anything else I can try?

If I setup a toolchain the following way, should Gradle automatically download a matching jdk if it can't find one already on the system:

jvmToolchain {
      languageVersion.set(JavaLanguageVersion.of(libs.versions.jdk.get()))
      vendor.set(JvmVendorSpec.AZUL)
}

Gradle is hosting a free Kotlin DSL Gradle webinar. It is a get intro to Kotlin with Gradle, our first time running such a training. Let me know if you have questions!

Is it possible to use context receivers with kotlin-dsl in gradle scripts? I saw that gradle 7.6 updated embedded kotlin to 1.7.10, but I still can’t use context receivers in gradle scripts:

java.lang.UnsupportedOperationException: Unsupported receiver value: Cxt { context(org.gradle.api.Project) [...]