Maybe it would be good to extend the existing tests for this case.

Review should consider this:
Lambda body can be a block or an (arbitrary) expression. So maybe the cases which are handled in the code are insufficient and should be replaced by handling the general org.eclipse.jdt.core.dom.Expression (see my similar comment in changed Java file).

please add a junit test. see /org.eclipse.jdt.debug.tests/tests/org/eclipse/jdt/debug/tests/breakpoints for related ones

Hi, @jukzi, I would try to craft a PR with a JUnit test but first I need a hint to make my Eclipse SDK working again. My initial setup with OOMPH was fine and I used it for several months. Now I have updated the SDK with the "Perform setup tasks" feature. After this I now have zillions of compile errors in my SDK because all/many of the external dependencies like JSoup are missing. How can I restore/recreate all these dependencies to get rid of the compile errors? Thanks in advance.

When i have such problems it helps to 1. pull all repositories, 2. use the "edit" button of the eclipse-sdk target platform to update it. 3. reload the active target platform. 4. rebuild all projects. Don't know why such is not done automatically @merks

Help -> Perform Setup Tasks... should generally update everything after pulling all the git repositories. The *.target file should be resolved automatically by those steps, but for unknown reasons (in PDE) that doesn't always work. :-(

Thanks for the quick response with valuable hints from experienced Eclipse developers. But they have produced some big question marks on my face. As you can see I need some more detailed info. Let's go through the steps.

1. Pull all repos: "Perform Setup Tasks" does this and I can also do it manually. CHECK
2. use the "edit" button of the eclipse-sdk target platform to update it: Where is this button located? Inside Eclipse? Never seen this before.
3. reload the active target platform: How to do this?
4. rebuild all projects: Have done this zillions of times before. CHECK

windows/preference:

Thanks. This procedure helped me out and resolved my compile errors. :)

Now I added a JUnit test.