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

Update org.checkerframework.annotatedlib:guava to Guava 33.1.0 #6531

Closed
hazendaz opened this issue Apr 9, 2024 · 1 comment · Fixed by #6546
Closed

Update org.checkerframework.annotatedlib:guava to Guava 33.1.0 #6531

hazendaz opened this issue Apr 9, 2024 · 1 comment · Fixed by #6546
Assignees

Comments

@hazendaz
Copy link

hazendaz commented Apr 9, 2024

I tried to look around for how this is done exactly but couldn't find the exact source location. The resulting checker.jar has shaded guava from known vulnerable version. Is there a hard requirement that is shaded and if so, can it be upgraded to latest release?

@mernst
Copy link
Member

mernst commented Apr 9, 2024

Thank you for pointing out this issue. I appreciate it.

One reason for the shading is explained at the very end of https://checkerframework.org/manual/#common-problems-running . Without shading, Error Prone and Nullaway break the Checker Framework, and other tools might too, and this applies to libraries as well.

I will upgrade the version of Guava that the Checker Framework uses, so that will be in the next release, which is planned for May 1 or earlier.

@mernst mernst changed the title Shaded Guava is listed as vulnerable by dependency check plugin Update org.checkerframework.annotatedlib:guava to Guava 33.1.0 Apr 9, 2024
@mernst mernst self-assigned this Apr 9, 2024
@mernst mernst linked a pull request Apr 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants