Hey there,
I found another jpackage difference since version 3.1.3.
According to the documentation, the jpackage jvm arguments should by default
use the jvmArgs value from the jlink launcher section, and only if that is missing,
the applicationDefaultJvmArgs from the application extension. At least that's
how I understand the following:
From the docs (https://badass-jlink-plugin.beryx.org/releases/latest/#_jpackage):
jvmArgs
list of JVM arguments to be passed to the virtual machine.
defaultValue: the jvmArgs value configured in the launcher block, or the
arguments configured in the applicationDefaultJvmArgs property of the application extension.
In the latest version the launcher jvmArgs are ignored and the applicationDefaultJvmArgs always used.
I've forked and updated the demonstrator from hungarian-notation in #349.
https://github.com/bjorndarri/missing-jvmargs-reproduction
Hey there,
I found another jpackage difference since version 3.1.3.
According to the documentation, the jpackage jvm arguments should by default
use the
jvmArgsvalue from thejlinklauncher section, and only if that is missing,the
applicationDefaultJvmArgsfrom the application extension. At least that'show I understand the following:
From the docs (https://badass-jlink-plugin.beryx.org/releases/latest/#_jpackage):
jvmArgs
list of JVM arguments to be passed to the virtual machine.
defaultValue: the jvmArgs value configured in the launcher block, or the
arguments configured in the applicationDefaultJvmArgs property of the application extension.
In the latest version the launcher
jvmArgsare ignored and theapplicationDefaultJvmArgsalways used.I've forked and updated the demonstrator from hungarian-notation in #349.
https://github.com/bjorndarri/missing-jvmargs-reproduction