Is there any intention to use "jpackage" to package applications under various operating systems?

[youngledo]

Currently "jifa" only supports Docker or shell scripts to run, which is not very convenient.

Starting from Java 14, it is supported to package a jar package (jpacket) into a runnable application. Please refer to: https://docs.oracle.com/en/java/javase/17/jpackage/packaging-overview.html#GUID-C1027043-587D-418D-8188-EF8F44A4C06A

I have tried successfully packaging under macOS with the following command:

jpackage --input ./lib --name "Eclipse Jifa" \
        --icon jifa.icns --vendor "Eclipse" --app-version 1.0.0 --main-jar jifa.jar \
        --java-options "'--add-opens=java.base/java.lang=ALL-UNNAMED' '--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED' '-Djdk.util.zip.disableZip64ExtraFieldValidation=true'"

At the same time, this configuration needs to be enabled:

The final effect, as shown in the figure:

[youngledo]

Of course, if you want to use "jpackage" you need to modify the build script(Sorry, I can't help but participate in the script modification, I haven't quite figured out how this build works).

[D-D-H]

Based on our internal usage experience, users are more inclined to deploy Jifa on servers, and they rarely have the need to deploy their own instances locally.

[youngledo]

This is not necessarily, as a personal analysis tool everyone installed is also very common. After all, there are many choices, nothing more than a variety of packaging methods.

[youngledo]

I have written a shell script for "jpackage"(the bat script needs to be improved):

To be continued...