Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Proguard (or anything similar) to shrink compiler size #104

Open
mosser opened this issue Feb 5, 2025 · 0 comments
Open

Using Proguard (or anything similar) to shrink compiler size #104

mosser opened this issue Feb 5, 2025 · 0 comments
Labels
maintenance related to CI/CD or code maintenance

Comments

@mosser
Copy link
Member

mosser commented Feb 5, 2025

The compiler is around 10Mb in size, which is still OK but could be improved by shrinking it a little bit. So far the "jar-with-dependencies" plugin create a compiler JAR file that contains ALL the libraries linked, even if we're not using everything from them.

We might want to consider using Proguard (or anything similar) to provide static analysis of the code and remove unused classes from the final jar file.

@mosser mosser added the maintenance related to CI/CD or code maintenance label Feb 5, 2025
@mosser mosser added this to the 2508 - Summer 2025 milestone Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance related to CI/CD or code maintenance
Projects
None yet
Development

No branches or pull requests

1 participant