Ship the app. Bring the runtime.

What is it?

A packaging tool that combines a JVM application and a minimal Java runtime into a self-contained executable.

What problem does it solve?

A practical answer to “install Java first”, with a distinction worth keeping clear.

What does it replace?

Potentially a separate Java installation step for the person receiving your application.

What doesn’t it replace?

GraalVM native compilation. Bundling a JVM is a different approach with different size and startup trade-offs.

Who is it for?

JVM developers distributing applications to people who should not have to configure Java.

The review notebook

Distribution is part of the product. If the first experience of an application is diagnosing a missing runtime, the developer has handed some of the packaging work to the user. Bundling can remove that burden.

The important comparison is with your current delivery process. We would measure the resulting file, time a cold launch and try it on a clean machine. There is no need to claim that one packaging strategy wins every workload for this one to be useful.

Known catches & open questions

Self-contained does not mean runtime-free. Size, runtime updates and target-platform compatibility still need attention.

Current judgement

This is a promising lead, not a recommendation. We will only make a hands-on judgement after the stated test has been run.

Next on the bench

Package a small application and run it on a clean machine without Java; check launch behaviour and record the bundled runtime version.

Sources & evidence

Project repository and README ↗
Release history ↗

Public material checked 5 September 2026. Version labels are the latest stable release returned at that check, where available. Platform descriptions are upstream claims, not Toolglass acceptance tests.