Spring exacerbates this because people will just wire anything in across architecture layers (for example controller -> repository instead of through a service layer). They just shove everything in one project. they do not make enough modules aka projects. This is a pattern I see with IntelliJ users. After a while this stuff all becomes muscle memory. I'm not normally a fan of programs that are infinitely customizable but Eclipse does a good job here: you can easily import/export your preferences and you can attach keybindings to everything leading to a mouse-free experience. Solid debugging when, at the end of the day, something terrible happens and you need to step through the code line-by-line to figure out what's going on.Įvery once in a while I try to open my system - which consists of ~30 multi-module projects and hundreds of modules - in Idea and then eventually get fed up with it.Įclipse also has a bit of an emacs effect going for it. Search all the projects, incrementally compile all the projects, refactor all the projects, support for projects that aren't even Java projects! The reasons to use Eclipse ultimately boil down to: IntelliJ's maven support cannot really handle such beasts. We've got modules nested within modules! Modules everywhere! Eclipse, armed with a minimal 4gb of memory, handles it like a breeze. Step Return (F7) – This operation finishes the current method and takes us back to the calling method.Dunno, but I'm starting to really hate IntelliJ for its poor support for Maven.In this example, this will execute the method isPerfectSquare() and proceed to the next line Step Over (F6) – This operation processes the current line and proceeds to the next line.In this example, it will take the debugger inside the method isPerfectSquare() Step Into (F5) – This operation goes inside the methods used in the current line (if any) else, it proceeds to the next line.The most commonly used debug options are: Let's assume that the debugger is currently positioned as per the below screenshot, at Line 16:

Now that the debugger stops at the given breakpoints, we can proceed with further execution.

How to use eclipse debugger spigot