Community
Participate
Working Groups
In Eclipse 4.28.0 (also previous versions) breakpoints inside lambdas will get pushed down to a seemingly arbitrary position outside at saving, if the same code line or one before was edited. An example would be lambda test functions from within JUnit jupiter (5.93./1.9.3) assertAll( () -> { ... // 2) edit code and save ... // 1) Breakpoint set ... }, () -> { 3) >> Breakpoint gets pushed here or below ... } ); Since breakpoints cannot be moved, this gets especially nasty, when conditional breakpoints are being moved and broken this way each time. JDK currently is Oracle JDK 11.0.18.
I should add, that repeatedly moved breakpoints stack up at the same line below, if not manually deleted each time (also showing up multiple times in the breakpoint view window) and the edited code line doesn't necessarily need to be inside the same lamda or maybe not even before the code line with the breakpoint. So, the problem is even more disruptive, since not only you'll have to re-create dedicated breakpoints each time, but additionally need to delete the "zombie"-breakpoints generated by Eclipse.