Debug Lombok

[savchenkoto]

Can I somehow debug Lombok sources?

[Reinier Zwitserloot]

Depends on the environment.

Debugging the eclipse agent: Agents have to be jars, and at least the eclipse hot-code-replace debugger isn't used to it. We specifically designed our shading class loader to be capable of loading resources off of your autocompile dir to make the impossible possible. To use this feature, This is the voodoo magic (these are vmargs to use for invoking your eclipse; use eclipse's tools to debug eclipses in eclipse to use this):

-Xms40m -Xmx512m -XX:MaxPermSize=256m -Dorg.eclipse.swt.internal.carbon.smallFonts -javaagent:${project_loc:lombok}/dist/lombok.jar -Xbootclasspath/a:${project_loc:lombok}/dist/lombok.jar -Dlombok.patcher.patchDebugDir=${project_loc:lombok}/debug/patchedClasses -Dshadow.override.lombok=${project_loc:lombok}/bin:${project_loc:lombok.patcher}/bin:${project_loc:lombok.patcher}/lib/runtime/*:${project_loc:lombok}/lib/runtime/*

Debugging javac: Should be possible; javac is in the end just a java app. You're in the same boat with the classloading issue (javac expects annotation processors to be annotations), but the same rules apply as above.

Debugging intellij or visual code: Those are plugins maintained by other programmers. I know the intellij plugin is (obviously) its own project designed to be worked on within intellij, and presumably intellij has tools to debug the writing of intellij plugins.