has the way to build a shadowJar changed since gradle 7.4 ? I'm running

gradle shadowJar

, but only getting a jar with a Manifest in it in my root

build.gradle.kts

, I have the shadow plugin

plugins {

   ...
   val shadowVersion = "7.1.2"

   kotlin("multiplatform").version(kotlinVersion).apply(false)
   kotlin("plugin.serialization").version(kotlinVersion).apply(false)
   id("com.github.johnrengelman.shadow").version(shadowVersion).apply(false)
}

and then in my module

plugins {
   application
   kotlin("plugin.serialization")
   kotlin("multiplatform")
   id("com.github.johnrengelman.shadow")
}

application {
	mainClass.set("com.blah.MyServer")
}

when running

gradle shadowJar

, I get a fatjar which only contains a manifest, nothing else, not even a class file, but when hitting run in IntelliJ, it runs perfectly fine. my jvm files are under

module/src/jvmMain/kotlin/com/blah/*.kt

what is the alternative to build fat jars? I've tried the zipping approach, but it too is doing the same

tasks.named<Jar>("jar") {
   archiveFileName.set("foo.jar")
   manifest {
      attributes("Main-Class" to "com.blah.MyServer")
   }

   from(sourceSets.main.get().output)

   dependsOn(configurations.runtimeClasspath)
   from ({
      configurations.runtimeClasspath.get().map { if (it.isDirectory) it else zipTree(it) }
   })
}

I have a question about the new

@ConstructedBy

and

RoomDatabaseConstructor

APIs in Room 2.7.0-alpha06. Would appreciate any insights.

Is there an example somewhere how parameter injection for a class while at the same time an interface (that is implemented by the class o.c.) is bound to the bean. I have the class

class DokumentMemoryPersistenceAdapter
    (entries: List<Dokument>) : LoadDokumentPort, SaveDokumentPort

and the module

val persistenceKoinTestModule = module(createdAtStart = true) {

    single {
        (entries: List<Dokument>) ->
        DokumentMemoryPersistenceAdapter(entries = get { parametersOf(entries) })
    } withOptions {
        bind<LoadDokumentPort>()
        bind<SaveDokumentPort>()
    }
}

In my test I do the following

@BeforeEach
    fun beforeEach() {
        println("BeforeEach")
        val entries = emptyList<Dokument>()
        val persistenceAdapter: DokumentMemoryPersistenceAdapter by inject { parametersOf(entries) }
    }

    @Test
    fun loadDokumentOkTest() {
        val loadDokumentPort by inject<LoadDokumentPort>()

but as a result I get a message "could not create instance for DokumentMemoryPersistenceAdapter" with a root cause

Caused by: org.koin.core.error.NoParameterFoundException: Can't get injected parameter #0 from DefinitionParameters[] for type 'java.util.List'
	at app//org.koin.core.parameter.ParametersHolder.elementAt(ParametersHolder.kt:41)
	at app//org.codeshards.aktenordner.adapter.outgoing.persistence.PersistenceKoinTestModuleKt$persistenceKoinTestModule$1$1.invoke(PersistenceKoinTestModule.kt:22)
	at app//org.codeshards.aktenordner.adapter.outgoing.persistence.PersistenceKoinTestModuleKt$persistenceKoinTestModule$1$1.invoke(PersistenceKoinTestModule.kt:14)
	at app//org.koin.core.instance.InstanceFactory.create(InstanceFactory.kt:51)
	... 81 more

Lines 14 - 22 of my module happen to be the singleton declaration. I also tried to supply the parameter for the injected interfaces along the following sample

val saveDokumentPort: SaveDokumentPort by inject { parametersOf(entries) }

and got the same results. A similar test without a bind option works

class ListPresenter(val a: List<Dokument>)

val presenterModule = module {
    single {
            (a: List<Dokument>) -> ListPresenter(a = get { parametersOf(a) })
    }
}
...
    @Test
    fun listTest() {
        val a = emptyList<Dokument>()
        val listPresenter: ListPresenter by inject { parametersOf(a) }

so I guess the bind option is the problem. Any feedback would be appreciated.

I’m wondering what I’m doing wrong when it comes to caching Gradle state between CI builds. Here’s an example: after making this change that doesn’t change any source code, still a full Gradle build occurred (see here). Since I use gradle-build-action, it states in its README that it does some caching. For the mentioned commit, I’d expect Gradle to complete within several seconds, inferring that no source code was changed (

UP-TO-DATE

). Any clues?

How do I deactivate rules? I get a lot of false positives and therefore want to exlude some rules. I created a file named

.editorconfig

in the top level of my project with the contents

# Don't autoformat this file, IntelliJ adds forbidden spaces
root=true

[*.{kt,kts}]
disabled_rules=indent,max-line-length
insert_final_newline=true

But indent and max line length is still checked.

The memory usage of the kotlin compiler daemon for our project reached 10Gb threshold. If we set it lower kotlin daemon dies out with OOM.  It dies during the kapt processing. That’s why I’m trying to reach out to this channel. Wonder if anyone else experienced similar issues. The heap dump looks pretty similar to the one in this issue (https://youtrack.jetbrains.com/issue/KT-32962). But there is no leak in our case. There is only one instance of IncrementalProcessingEnvironment. Also with 10gb heap limit the memory goes down to normal level after annotation processing finished. We had a suspicion that it had something to do with the generation of the @Metadata annotations on the stubs (A big chunk of heap is consumed by the flatbuffer strings). We did a quick hack to strip those annotations out of stubs generated by kapt but it doesn’t seem to be helping much. We have a BUCK build configured and it doesn’t have such problem (it doesn't use kotlin daemon though). Right now we have to hypothesizes: 1. There is something wrong with our gradle script or kotlin gradle plugin. It would be awesome if someone could give a pointer how to enable the logs of the kotlin daemon launched from the gradle plugin, ie how to tweak the verbosity level of the daemon and where to find logs on Mac/Linux. 2. It might be the case that kapt extension keeps more resources than it is needed for the processing. Currently the code for the resources release in kapt looks like this (https://github.com/JetBrains/kotlin/blob/2552540f7165571dd2fdefdef4f09d858e4fa92a/plugins/kapt3/kapt3-compiler/src/org/jetbrains/kotlin/kapt3/Kapt3Extension.kt#L101-L104). We wonder if there is a way to say release some of the resources between different annotation processors runs?  Most of our codebase is Kotlin, so literally every file in the project has the Metadata annotations and corresponding overhead. Is there a way to ignore those data completely during the kapt processing? What would be consequences of doing it? Maybe there are some known kapt options that could potentially help mitigate the issue/reduce the memory footprint? Our gradle.properties for kapt now:

# See: <https://youtrack.jetbrains.com/oauth?state=%2Fissue%2FKT-17621>
kotlin.incremental.usePreciseJavaTracking=true
# Configure the Kotlin Gradle plugin to run tasks in parallel within a project.
# <https://blog.jetbrains.com/kotlin/2019/01/kotlin-1-3-20-released/>
kotlin.parallel.tasks.in.project=true
# There is a cache key inconsistency when enabling this
# Disable incremental kapt locally to avoid this
# <https://youtrack.jetbrains.com/issue/KT-31840>
kapt.incremental.apt=false
# Skips annotation processing completely when there are no changes in kapt stubs and only method
# bodies are changed in dependencies. See <https://blog.jetbrains.com/kotlin/2019/01/kotlin-1-3-20-released/>
kapt.include.compile.classpath=false

I've never used dagger/hilt in a multi-module setup. Lets say I have

app

gradle module which depends on

service

. And

service

inside has

SomeServiceClass

. Would

service

gradle module have a @Module and @Provides, providing the

SomeServiceClass

to

app

gradle module? Or is it more customary for the

service

gradle module to declare what it provides?

I am trying to migrate my gradle to the gradle hierarchies. I am getting error:

kotlin {
    androidTarget() // <-- please register this Android target
}

When if I put

androidTarget()

gradle says

Unresolved reference: androidTarget

I cleaned my cache. And I have the template project from the Jetbrains wizzard tool which works just fine with androidTarget(). I am missing something I don't understand what exactly.

kotlin.version=1.9.20
agp.version=8.1.2
distributionUrl=https\://services.gradle.org/distributions/gradle-8.4-bin.zip

Any hints?

Why is SSL necessary for HTTP2? The protocol doesn't need it. I have a proxy before the server, but I can't use HTTP2 because Ktor doesn't know about it.

Hi everyone, I’m facing error while calling Ktor API

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".

SLF4J: Defaulting to no-operation (NOP) logger implementation

This error doesn’t come when i pass HashMap<String, String> to body But whenever i’m passing,

HashMap<String, Any>

then only getting error. Any idea? Do I need to add SLF4J dependency🤔