-
Notifications
You must be signed in to change notification settings - Fork 9
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
Downstream build fails when using annotation processor and compile options -Xlint:all -Werror
#342
Comments
I had originally claimed the annotations but errorprone says that is bad. I may need a flag. I’ll get this fixed for very soon. |
https://errorprone.info/bugpattern/DoNotClaimAnnotations I will check with the errorprone team as well. I swore I have |
Here's a proof of concept build as well as the workaround (Adding |
I didn't know this was problematic .. 🤷 I'm looking forward to errorprone's reply 👌 |
Apparently my other project had a flag to disable the warning but for a different reason. Would adding an annotation processor flag be amenable for now? Annotation processors look like The issue is I can't add this till like at least a minor release and not a bug release. The flag I can add as a bug release (well semver is sort of unclear on this because its not actual runtime but lets ignore that) which will not impact people relying on the annotation for whatever reasons. Also how urgent is this for you? |
Using |
Yes that is the flag I have set in the other project. I will eventually add a flag as I can see an advantage to still have the warning applied to other processors. Thanks for the bug report! |
Using the annotation processor in a build along with compiler options
-Xlint:all -Werror
fails the build with:Similar issue to the one solved in project lombok here.
The text was updated successfully, but these errors were encountered: