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
org.checkerframework:checker-compat-qual appears unused in many modules #3006
Comments
This is intentional. We noted in the release notes that we added this dependency without using it, but we didn't explicitly call out that we intend to use it in the next release. I'll note that now. |
Sorry, posted too early. More in a moment. |
Sorry that it's breaking your build. I initially thought you were saying that your build was failing specifically because it was detecting an unused dependency, but that doesn't seem to be the problem. But I'm not sure what the problem is. Are there other ERROR lines in your log? |
Unfortunately the failure is pretty inscrutable. It's not happening on our OSS plugins so there must be some internal Maven configuration we're doing that's messing with it. Here's the stacktrace from running maven with
|
Maybe try upgrading to |
That does seem to be the issue, I pushed a reproducible example here. If you clone and run |
Good call. Done. |
Thanks for your help, Chris! |
org.checkerframework:checker-compat-qual
appears to be unused under both the jre and android flavors ofguava
andguava-tests
but is listed as a dependency in those poms.The
org.checkerframework:checker-compat-qual:2.0.0
jar contains.class
files with eitherorg.checkerframework
orafu.plume
in their packages. I see the following, which makes me think this is safe to remove this dependency from the above modules:I came across this because our in-house maven plugins were failing to compile after upgrading to
23.5-jre
and excludingorg.checkerframework:checker-compat-qual
from guava seemed to fix the issue. An example build failure is:The text was updated successfully, but these errors were encountered: