Serban Iordache

They fixed a couple of bugs in jpackage 16. I'm curious if you get the same error. Also, when testing with jpackage 16, please add the --verbose option: ``` jlink...

Can you also post the complete output of the `jpackageImage` task? It should include a dump of the `taskData` and the jpackage command.

You should use the org.openjfx.javafxplugin, as shown in [this example](https://github.com/beryx-gist/badass-runtime-example-javafx/blob/14c94d7251947a2f6fe781b92ba2c885fcafc857/build.gradle#L3).

I'm not able to reproduce this issue. Do you get the same error when executing `./gradlew runtime` on the [badass-runtime-example-javafx](https://github.com/beryx-gist/badass-runtime-example-javafx) project?

Add the `--verbose`option to your build script: ``` jlink { ... jpackage { .... installerOptions += '--verbose' } } ``` Then, execute: ``` ./gradlew -i jpackage ``` This will print...

Try also adding this: ``` jlink { ... jpackage { .... installerOptions += ['--app-version', version.replace('-', '.')] } } ```

Now add this: ``` jlink { ... jpackage { .... installerType = 'rpm' } } ```

No need to worry. In verbose mode jpackage shows many warnings and errors but the relevant ones were: ``` error: line 3: Illegal char '-' in: Version: 0.1-SNAPSHOT ``` and...

That's not ok. Is the java executable available in ensia/lib/runtime/bin? Can you execute `/home/sukma/workspace/project/oss/ensia/build/jpackage/ensia/lib/runtime/bin/java`?

The jlink setup looks good. I don't know where the error message comes from. A google search for "Failed to find JVM in" returns no results. Is it possible that...