I have a multiplatform project where in one of the modules I use some features that need an `--add-o...

# gradle

[loke]

I have a multiplatform project where in one of the modules I use some features that need an --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?

[ephemient]

1.

tasks.test {
    jvmArgs(listOf("--add-opens", "..."))
}

2. you can try adding to JAVA_TOOL_OPTIONS outside of Gradle which will apply to all Java launches, but there's no configuration for forwarding JVM args to dependent modules

[loke]

Thanks

[loke]

Let me try

[loke]

Hmm, could not find method test(). Where do I actually put this?

This is the module in question by the way: https://codeberg.org/loke/array/src/branch/master/contrib/arrow/build.gradle

[loke]

Ah wait. Not .test but rather .jvmTest it seems.

[Vampire]

Yeah, KMP is different 😄

[loke]

Also, listOf doesn't work. I needed to use += "...". I guess listOf would be for the Kotlin syntax.

[ephemient]

if it's Groovy DSL and not Kotlin there's other changes too

[loke]

Is there a way to disable all the --add-opens nonsense in the JVM and get it to work like old Java used to work?

[ephemient]

nope

[loke]

So in my case, where I have a set of jar files that users can add to get extra functionality, I can't just have the users drop the jar files in a modules directory, but I also need them to add a parameter on the commandline. Surely I'm missing something here.

[Vampire]

Sure, use old JVM 🙂

[Vampire]

Btw. iirc it would be more like

kotlin {
    jvm {
        testRuns.configureEach {
            executionTask {
                jvmArgs(...)
            }
        }
    }

idiomaticly

[ephemient]

well if it's another module I think you could use module-info.java. but JPMS doesn't play well with KMP afaik, and that doesn't let you open Java internals

[loke]

I see. Thanks.

[loke]

I need to read up on the module stuff. I've avoided it for a long time.

[ianbrandt]

Loosely related, but in case it's of any interest, I have a thread over in #C07SN33NTFA where I'm tracking Kotlin issues that are blocking us from migrating our mixed Java+Kotlin suite of server-side and desktop apps to JPMS: https://kotlinlang.slack.com/archives/C07SN33NTFA/p1729282775524889.

If any of those issues impact others, I'd encourage you to upvote them. Despite being an integral part of the JVM platform, JPMS support doesn't seem to be much of a priority on Kotlin's roadmap.