JPackage is a way to package a modern JVM-program as a installable binary, in a small format.
JPackage was finally included in the JDK by JDK-14, originally from the JavaFX-world (to bundle your desktop apps). JPackage combines itself with JLink, which builds upon 'project jigsaw', and together they form a way to create \"native\" binaries for JVM-projects.
What is JLink?
JLink is a way to assemble and optimize a set of modules and their dependencies into a custom runtime image (JRE). In other words we can take a ordinary JRE, ~200 MB, and chop it down to a total size of 25-40 MB for smaller project.
JLink is only possible thanks to 'project jigsaw' which introduced modules and modularized the whole JRE starting from JDK-9. The Java standard library (stdlib) was modularized into 75 modules. As you might guess it is even better if your own code is also modularized, but not enforced.
What is JPackage
JPackage is the packaging suite that allows you to package your code, dependencies and the JLink-created JRE. I ended up with installation files, with a natively executable file on 60 MB for one of my smaller projects, which is really good in comparison to Electron! In comparison to a C-program this might not be amazing, but you've to remember that this is completely cross-platform!
Side-note all sized discussed is without any major optimizations - and there exists a lot! Finally, if you exclude the JRE you can reach sizes of KB rather than MB! But excluding the JRE enforces the user to have it locally, which might not be good UX.
Make sure you use & target JDK 14 or higher, JPackage was first included in this version. I recommend SDKMan to install & swap JDKs.
Then to add the
Badass Runtime Plugin I recommend using
gradle, which makes it as simple as the following.
id(\"org.beryx.runtime\") version \"1.11.3\" // latest version August 2020
options.set(listOf(\"--strip-debug\", \"--compress\", \"2\", \"--no-header-files\", \"--no-man-pages\"))
installerType = \"deb\" // https://badass-runtime-plugin.beryx.org/releases/latest/
This addition now creates the tasks required to build & bundle your app. The options added make sure that you reduce the total size by a lot. I highly recommend reading the documentation, there's so many incredibly useful options - I only provide the minimum!
By editing our
building.gradle.kts to include everything from the Installation we can run the
./gradlew jpackage task to build our installer!
I want to note again, please make sure to read the homepage - a ton of optimizations and customization exist. There exists a lot of low hanging fruit for sure, so make sure to grab it! 😉
It's really cool to see your JVM application installable using a
.deb or even a
.dmg while retaining a decent enough size.
By using JPackage rather than GraalVM you make sure that you don't loose anything in the form of performance or functionality. As a cherry on the top, it's not just a executable file, but also includes a installer which is much better UX in my opinion. GraalVM will be discussed a bit more in Alternatives.
I want to re-iterate about the UX and size, which are the two main points of this.
- We bundle a JRE with the JVM-app, allowing executables without requiring Java, of your version, to be installed on the user computer already.
- The JRE is minified to only contain required modules, about 30-40 MB on a smaller project.
- All required dependencies are bundled also
- Installer which makes the whole JVM program really like any program on the computer
- Basically a download, install run program that isn't huge in size!
I see two alternatives that are worth mentioning
- FAT-JAR / Uber-JAR / Shadow-JAR
- GraalVM Native Image
A FAT-jar is a jar that bundles all dependencies and also includes a shell script, or
.bat if Windows, to run the whole JVM-application.
It's pretty small in size, even though called FAT, as it doesn't include a JRE to run the JVM.
This means that if your JVM-app requires Java 11 but the user only has Java 8 you need to have them download the JRE required, which sucks.
The probably best alternative, it's even smaller in size as SubstrateVM (their runtime) is really small and GraalVM allows AOT compile.
GraalVM has much faster startup-times than a JPackage program, but GraalVM is not as good when running for a long duration as there isn't the incredibly good JIT from JVM.
I'd say something along the following - for long running apps choose JPackage, for lambda etc certainly choose GraalVM.
But GraalVM has further negatives, you can't just code as you usually do. Reflection etc is not supported as usual, meaning there comes a lot of caveats using GraalVM.
Extra: I managed to end up with, after some minor trial-and-error, a binary file on ~ 12 MB for my file-sending program - pretty darn amazing!
I'll write more about GraalVM and its SubstrateVM which is used to create the native binaries in a new TIL.