This reverts commit 04c9755b39.
The nature of the fix is to simply scan the TypeMirror for 'lombok shenanigans'; if it finds them, the type is not complete; if there are none, the type is.
This fundamentally does not work - lombok shenanigans may remain even if lombok is done (`@lombok.NonNull` for example), and lombok shenanigans don't just appear as annotations on the type; they can appear in many forms: Annotations on local var decls, or even method calls to `Lombok.safeDeNull` or whatnot. safeDenull is made up, but we might add it someday. `@Getter` on a field isn't though, and suffers from the same problem.
Project Lombok
Sponsored Content
Offer API docs that look as good as Stripe's using our sponsor Fern. Request a preview of your docs on Fern.
Project Lombok is a java library that automatically plugs into your editor and build tools, spicing up your java. Never write another getter or equals method again, with one annotation your class has a fully featured builder, automate your logging variables, and much more.
See LICENSE for the Project Lombok license.
Looking for professional support of Project Lombok? Lombok is now part of a tidelift subscription!
For a list of all authors, see the AUTHORS file.
For complete project information, a short tutorial on what lombok does, and how to download / use / install it, see projectlombok.org
You can review our security policy via SECURITY.md
