Serban Iordache

@sunsteam I don't think that this is possible. But did you try to build your application using [JDK16 Early-Access](https://jdk.java.net/16/)? The jpackage bug should be fixed in this version.

I created [an example project](https://github.com/beryx-gist/badass-runtime-issue-71). You need the [latest JDK 16 Early-Access Build](https://jdk.java.net/16/).

@sunsteam The above solution should fix your problem. However, it is only a workaround. I discovered the real cause of the error and I reported it on the OpenJDK mailing...

Strange... I'm not able to reproduce the problem with neither [this](https://github.com/beryx-gist/badass-runtime-example-javafx/actions/runs/277195113) nor [this](https://github.com/beryx/fxgl-sliding-puzzle/actions/runs/277152686) project.

In 2.22.1 mergedModuleJarVersion and mergedModule.version have the same meaning: they configure both the module version of the merged module and the suffix of its jar name. However, mergedModuleJarVersion is now...

Oh, right, version 2.22.2 was really broken. I now released 2.22.3, which should fix the error.

@msgilligan What error do you get?

The `customImage` block was not compatible with jpackage. I fixed this in 2.23.1.

@nemphys What error do you get when using jpackage 16?

No, I really meant jpackage 16. You can download an [Early-Access Build](https://jdk.java.net/16/) and use one of the methods [described here](https://badass-jlink-plugin.beryx.org/releases/latest/#jpackageHome) to configure your project to use the jpackage tool from...