Java / Lombok Interview questions
How do you debug generated Lombok code?
Since the generated methods don't appear in your source file, stepping through them in a debugger or
inspecting exactly what was generated requires a couple of specific techniques rather than just reading the
.java file.
# view the actual generated code as plain Java: delombok src/main/java -d src/delomboked # or inspect the compiled .class file's bytecode directly: javap -c -p target/classes/com/example/Person.class
delombok (Lombok's own tool) converts your annotated source into an equivalent, fully expanded
plain-Java source tree with no Lombok annotations at all — the clearest way to see exactly what code was
generated. Most modern IDEs with Lombok plugin support also let you step into generated methods directly in the
debugger, since the plugin makes the IDE aware of them, though the "source" it shows during debugging is
often a synthesized view rather than a literal file on disk.
What does the delombok tool produce?
What can javap -c -p help you inspect for a Lombok-generated method?
More Related questions...
