I could really use some help, I don't understand why main runtime dependency is returning a config while the test runtime dependancy is, correctly, producing a file collection..... oddly enough this task doesnt run unless the classpath is set to the test one which makes no sense!

I would suggest using code navigation to explore the plugin source

Is there a way to do that in intelliJ since the plugin is just a string ?

kotlin("multiplatform") version "1.3.70"

Cmd (Cntrl) + left click

yeah, doesnt usually work on libraries defined by strings and thats what gradle uses

you can literally click on the property you're asking about,

runtimeDependencyFiles

yes I know, sorry... it just doesn't tell me anything. This really makes no sense why test would work but main wouldn't... almost like they are backwords

not to me

I figured it out I guess, just by jiggling it I guess. I had tried this before but was getting error on main = ""... I changed it to setMain and it magically worked. Still though I feel like there is another way to create a task outside of the jvm() object based on the docs, but I don't really get it... that was painful, thanks for the emotional support 😃

jvm("backend") {
    compilations {
        val main by getting

        val runApplication by compilations.creating {
            tasks.register<JavaExec>("runApplication") {
                group = "fl"
                setMain("com.company.ApplicationKt")
                classpath = main.compileDependencyFiles + main.output.classesDirs + output.allOutputs
            }
        }
    }
}