`jbang run <jarFile>` ignores `Enable-Native-Access` property in the manifest.mf file

[wfouche]

If the JAR file is executed using java with command

• java -jar <jarFile>

the attribute Enable-Native-Access entry in the manifest.mf file takes affect, but when run with JBang

• jbang run <jarFile>

it is ignored.

Enable-Native-Access: ALL-UNNAMED

[wfouche]

Java 22+ supports option --enable-native-access=ALL-UNNAMED. The logic to be applied seems to be as follows:

• If the JAR file to be executed contains attribute Enable-Native-Access: ALL-UNNAMED in manifest.mf, then if Java 22+ will be used to run the application, then also add --enable-native-access=ALL-UNNAMED to runtime-options.

• The JAR to be executed is either determined directly by it having been specified explicitly, or indirectly if the JAR containing the main class to be run contains a manifest.mf file which has attribute Enable-Native-Access: ALL-UNNAMED defined.

[maxandersen]

Yes except the latter. Are you sure the jdk honors that attribute for anything but the primary jar? That would be surprising.

Possibly done for when running as modules?

[wfouche]

Are you sure the jdk honors that attribute for anything but the primary jar?

It is only for the primaryjar. I updated the comment above.