INSTALL4J MAC JRE BUNDLE UPDATE
INSTALL4J MAC JRE BUNDLE FULL

And, even then, maybe not if a compatible JVM is already present.

This is a special case that will be resolved in an upcoming release by making the installer use a JRE that is compatible with the app to avoid the double download.Īnyways these are 'fixed costs'. This was just an issue with the installer not needing JavaFX so downloading a non-javafx JRE first - but then the app needing JavaFX, so downloading one with JavaFX. > as others pointed out, downloading two apps from the samples already shows the problem).

INSTALL4J MAC JRE BUNDLE FULL

And an app that doesn't need the full JDK can still use the JDK. An app that doesn't need JavaFX can still use the JRE with JavaFX. For each of those there is a JRE/JDK option, and a JavaFX option. Currently it supports Java 8, 11, and 17. > This method of distribution doesn't work when pretty much all apps are almost guaranteed to used a different JVM No different than if the user downloaded and updated your app manually. If your app needs to 'transition' its resources when new versions are run, then that is up to you. When your app runs, it is always running a particular version of the app. For simplicity, I haven't exposes some of that yet. Other variations are possible too, such as only autoupdating minor updates. It is also possible to peg your app to a particular version so that it doesn't auto update. They are kept in $HOME/.jdeploy/packages/YOUR-PACKAGE/VERSION

You can have two versions installed simultaneously. When it downloads a new version, it doesn't overwrite old versions. If it already has a JVM that meets the requirements, it uses it. If it doesn't have the latest version, it will download it. It compares this with what it has installed. This will tell it the latest version, and also the JVM requirements (e.g. The launcher gets the package's metadata from npm's registry on launch. Used to use Adoptium but switched for JavaFX support reasons.Īny of these pieces could be switched out pretty easily (npm -> self hosting, Zulu -> Adoptium, or self hosted, bundled VM, etc.). (But it reuses JVMs so if it already has one that meets requirements, it will use that). If it needs to download a compatible JVM it downloads it.

INSTALL4J MAC JRE BUNDLE UPDATE

If the app needs to be updated, it will update it. The launcher (written in C and Go) checks the npm registry to get the app's metadata (e.g. > What are the single points of failure for the curated JRE procurement? In an earlier iteration (I've been at this for a couple years), it was self hosted, but I found that npm brought a lot to the table and simplified things, so I focused on that. I've seen some interest for self hosting, so it will likely be added. Assuming I'd rather self-host instead of hitching a ride on npm - could it it still be useful, as a cross-platform bundle maker?

Install4j mac jre bundle