-
Notifications
You must be signed in to change notification settings - Fork 746
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
UnusedNestedClass leads to NullPointerException (with repro) #1240
Comments
Catched same problem. |
6 tasks
33 tasks
I think I have a fix. |
Merged
nick-someone
pushed a commit
that referenced
this issue
Oct 9, 2019
This solves a problem with UnusedNestedClass on module-info.java files. Fixes #1240 Somewhat relevant to google/guava-beta-checker#8 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=273590160
nick-someone
pushed a commit
that referenced
this issue
Oct 9, 2019
This solves a problem with UnusedNestedClass on module-info.java files. Fixes #1240 Somewhat relevant to google/guava-beta-checker#8 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=273590160
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
I'm trying to export a package containing a nested static inner class through
module-info.java
. This seems to trigger theUnusedNestedClass
rule (which it shouldn't, as the inner class is public and therefore exported, but this is probably a separate problem). This leads to the following stacktrace:Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
mvn clean package
to see the error messageexports org.example;
tomodule-info.java
does not make a difference to trigger the error.requires java.base;
frommodule-info.java
makes it work somehow (adding any other requires clause seems to also make it fail).What version of Error Prone are you using?
2.3.3
java --version:
Have you found anything relevant by searching the web?
No.
The text was updated successfully, but these errors were encountered: