Quý khách vui lòng nhập thông tin để nhận
ưu đãi mới nhất từ FPT Telecom!
| Task | Command |
| :--- | :--- |
| Basic info | java -jar quark.jar info app.jar |
| Visualize method | java -jar quark.jar flow -c Class -m method app.jar |
| Safe squash | java -jar quark.jar squash --input app.jar --output opt.jar |
| Aggressive squash | java -jar quark.jar squash --level aggressive --input app.jar |
| Keep resource files | --keep "*.xml" |
quark.jar may not be the most famous tool in the Java ecosystem, but for the discerning developer who values insight over blind optimization, it is indispensable. Download it today and look into your bytecode like never before.
Have a tip or a bug report? Contribute to the Quark project on GitHub or check the official documentation.
| Approach | Time Required | Risk | Result |
| :--- | :--- | :--- | :--- |
| Manual dead code removal | Days/weeks | High (human error) | Moderate |
| ProGuard | 1 hour | Medium (reflection issues) | Excellent (size) |
| quark.jar | 5 minutes | Low | Good (size + clarity) |
For mission-critical financial or medical software where reflection is widely used, quark.jar is often the safer choice over full obfuscators.
The flagship operation. This reduces size and improves startup time.
java -jar quark.jar squash --input original.jar --output optimized.jar --level aggressive
What happens under the hood:
Real-world result: A Spring Boot thin JAR (15 MB) was reduced to 11 MB (27% reduction) with zero functional changes.
This is quark.jar's killer feature. Generate a PNG flowchart of a specific method to understand complex legacy code.
java -jar quark.jar flow -c com.example.PaymentProcessor -m calculateTax -o tax_flow.png my-application.jar
What you get: A color-coded diagram where:
Use case: Reverse engineer a closed-source library or document a 15-year-old internal module.
Error: java.lang.IllegalArgumentException: Unsupported version 65.0
Cause: quark.jar v2.1.0 supports up to Java 21 (version 65). Java 22+ code will fail.
Solution: Downgrade your target class files to Java 21 using --release 21 in javac.
For a deeper understanding, you might decompile the JAR. Tools like JD-GUI, Jadx, or Fernflower can help. This process can provide insights into the code but be aware of potential complexity and licensing implications.
For projects where quark.jar is used, tools like JDepend, Structure101, or dependency-check can provide insights into how the JAR integrates with other parts of the project.
