Variations like Limestone, Shale, and Jasper.
| Feature | ProGuard | quark.jar | JProfiler | | :--- | :--- | :--- | :--- | | | Yes (aggressive) | Yes (conservative, safe) | No | | Bytecode visualization | No | Yes (unique) | No | | Runtime profiling | No | No | Yes | | JAR size reduction | Up to 90% | 15-40% | 0% | | Learning curve | Steep | Moderate | Moderate | quark.jar
To understand why quark.jar is special, you must understand Quarkus’s unique output layout. Unlike a Spring Boot "fat JAR" (which includes all dependencies as nested JARs inside a single file), Quarkus splits the deployment into three distinct directories: Unlocking Java Microservices: The Complete Guide to quark
Traditional frameworks package everything into a single Uber-JAR. Quarkus deliberately avoids this for quark.jar for two major reasons: This gives you a baseline
It will display a tree view of the package structure and allow you to browse through classes.
This command will list the contents of the JAR file, including the files it contains and their sizes.
quark‑sql (Calcite integration)This gives you a baseline. A high dead-method percentage (>5%) makes this a good candidate for squashing.