Francisco Vargas Ruiz

I hope the main issue (Find module exception) could be fixed with issue #259 (adding JPMS support, when the plugin deals better with Java modules)

Hi @kerner1000! You can use your own `Info.plist.vtl` template ... just create the file `${assetsDir}/mac/Info.plist.vtl`. Is this valid for you?

It seems you are enjoying a lot contributing to JavaPackager 😃

Hi @Osiris-Team! I'm not really sure what you are proposing here ... I've read your changes in PR #248, but I don't know what are `jdkVersion` and `jdkVendor` for. Do...

`jdkPath` is already optional ... if not specified, JavaPackager uses the current JDK (`java.home`).

How is this feature going on? I've tried to test pr-248 branch, but it seems you have some work in progress. I plan to add some other features and patches,...

Hi @kerner1000! Thanks so much for your contribution. I'm not able to try on Mac OS right now ... please, can you confirm that the version of the plugin in...

Hi @umjammer! I'm sorry ... I fear I reintroduced an old issue 😞 On the one hand, there's a new feature in version 1.6.7 that allows you to select the...

A possible work around could be to use `macConfig.macStartup=UNIVERSAL|X86_64|ARM64` instead of `SCRIPT`. Please, try this and give us some feedback. Thanks!!!

Fixed in devel branch (JavaPackager 1.7.0-SNAPSHOT).