-
Notifications
You must be signed in to change notification settings - Fork 119
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
auto-value is included in the dependency #2807
Comments
Hi @KengoTODA, Closing this as non-actionable. Feel free to reopen if you have any action items for the client library team. |
Hello, thanks for your quick response! 🙌 I believe it has action items; users surely have a workaround but it is better to be fixed on the project side. Is there some reason to keep this dependency as compile scope? And it seems that I have no permission to reopen this issue. Do I need to open another issue? Thanks in advance! |
As recommended in the user guide for auto-value, the library imports the auto-value dependency with a provided scope. But looks like the flattening of pom before release is resulting in this dependency being listed as compile time dependency in maven central. Thanks for bringing this to our attention. |
It seems that the
auto-value
is included in the dependency, and it makes runtime images (e.g. shaded jar files) unexpectedly large.This package is used only in compilation time, so it is better to remove it from the runtime classpath.
Environment details
This issue is not related to the environment.
Steps to reproduce
./gradlew dependencies
ormvn dependency:tree
Any additional information below
User may apply a workaround as follows:
The text was updated successfully, but these errors were encountered: