Question 1

Packr vs jpackage: which should I use for Java app distribution?

Accepted Answer

Packr is simpler and offers more control over JRE minimization, but jpackage is officially supported by OpenJDK and integrates better with modern Java tooling. For new projects, consider jpackage unless you need Packr's specific features like ZGC support or libGDX optimization.

Question 2

How to minimize JRE size with Packr for Java 8 apps?

Accepted Answer

Use the --minimizejre flag with profiles like 'soft' or 'hard' provided by Packr, which remove unused JRE components. However, for Java 11+, you should create a minimized JRE separately with jlink before using Packr.

Question 3

Does Packr support Java 17 or later versions?

Accepted Answer

The README mentions support for Java 14+ and ZGC, but only Adopt OpenJDKs 8, 11, and 15 are tested. It likely works with newer versions, but compatibility isn't guaranteed, so you may need to verify with your specific JDK.

Question 4

How to set icons for Windows executables in Packr?

Accepted Answer

Packr does not set icons automatically for Windows or Linux; you must manually modify the output files post-packaging. This is a noted limitation in the README, requiring additional tools or steps.

Question 5

Can Packr handle self-updating applications?

Accepted Answer

No, Packr focuses on static bundling without update mechanisms. For self-updating packages, alternatives like Conveyor are recommended, as mentioned in the README.

Question 6

What are the security risks of bundling a JVM with Packr?

Accepted Answer

Bundling a JVM can expose users to security vulnerabilities if the JRE isn't kept updated, similar to other runtimes. The README links to a discussion on this, so consider your app's security needs and update policies.

Packr

What is Packr?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions