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

New JPMS enabled releases double the size of jar file #7743

Closed
2 tasks done
norrisjeremy opened this issue Mar 25, 2025 · 3 comments
Closed
2 tasks done

New JPMS enabled releases double the size of jar file #7743

norrisjeremy opened this issue Mar 25, 2025 · 3 comments
Labels
type=defect Bug, not working as expected
Milestone

Comments

@norrisjeremy
Copy link

Guava Version

33.4.5-jre

Description

The size of the new JPMS enabled releases double the size of the jar file.
This appears to be due to the fact that every class is duplicated in the multi-release directory META-INF/versions/9, instead of just putting module-info.class in the multi-release directory META-INF/versions/9.

Example

$ du -hs guava-33.4.0-jre.jar
2.9M	guava-33.4.0-jre.jar

$ du -hs guava-33.4.5-jre.jar
5.9M	guava-33.4.5-jre.jar

Expected Behavior

JPMS enabled releases should only grow barely in size, due to the addition of a single new module-info.class.

Actual Behavior

JPMS enabled releases double the size of the jar file.

Packages

No response

Platforms

No response

Checklist

  • I agree to follow the code of conduct.

  • I can reproduce the bug with the latest version of Guava available.

@norrisjeremy norrisjeremy added the type=defect Bug, not working as expected label Mar 25, 2025
@norrisjeremy
Copy link
Author

Appears this is a known issue that will be remedied in 33.4.6.

@cpovirk
Copy link
Member

cpovirk commented Mar 25, 2025

Thanks, a new issue would have been a better way for me to handle this report.

[edit: Here was the earlier discussion.]

@norrisjeremy
Copy link
Author

norrisjeremy commented Mar 25, 2025

Yes apologies, I searched the issues (both open & closed) and didn't see it reported, so I opened this, not thinking to check the release notes.

@cpovirk cpovirk added this to the 33.4.6 milestone Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type=defect Bug, not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants