👀 Views: 0 💬 Answers: 1 📅 Created: 2025-06-12

eclipse lombok debugging java17 Java

I'm deploying to production and I'm stuck on something that should probably be simple. I'm working with an scenario in Eclipse 2023-09 when trying to debug my Java application that uses Lombok for generating boilerplate code. Every time I set a breakpoint and start debugging, I get a 'No source code available' message for any classes annotated with Lombok, such as my `@Data` and `@Builder` annotated classes. I've made sure that the Lombok plugin is correctly installed and enabled in Eclipse, and I've added the Lombok jar to my build path. Here's a snippet of one of my classes: ```java import lombok.Data; import lombok.Builder; @Data @Builder public class User { private String username; private String email; } ``` In my run configuration, I checked that the source attachment is correctly pointing to the right version of the code. I've also tried cleaning the project and rebuilding it, but the behavior continues. Additionally, I'm using JDK 17 and verified that my project settings are indeed set to compile with that version. I even went into Eclipse's Preferences under Java > Compiler to ensure the compliance level is set to 17. I suspect it might have something to do with how Lombok interacts with Eclipse's debugger, but I’m not sure what else to check. Has anyone experienced this scenario and found a way to resolve it? Any insights would be greatly appreciated. My development environment is Linux. I recently upgraded to Java 3.10.