> With IntelliJ you need to look for these.

Erm what? Click "build", and IntelliJ shows all compilation errors with their locations

IntelliJ also does on-the-fly compilation and checking, at least if you enable it - which may be a performance problem for huge projects, but definitely not for students.

In eclipse, you dont have to press anything. You have prominently "problems view" where they are all listed as you type essentially. You dont have to expand nodes and errors are sorted all on top. (And you can filter them in millions ways, easily, make multiple copies of the view with different filters if you want.)

Then you see them in package/project view too. Each package, project and file with error has red icon with it.

IntelliJ does not show them in project view at all. It shows them only after you pressed "build", so you need to develop the habit of pressing it constantly. Oh, and the console shows exactly one error. The others are hidden in separate view view, inside collapsed nodes and you have to click multiple times to see them.

> IntelliJ does not show them in project view at all. It shows them only after you pressed "build"

It does better than that: it shows them directly inline with your code, with all the tips and hints and refactorings to make it work.

When you change something to be incompatible with existing code, it will immediately show a handy link inline to display all the places across your code that depend on this code and are now problematic.

There's a problems view that has an overview of all problems in the current file and in the entire project (but true, a single overview of the entire project only appeared sometime in 2020)

What you are describing is quite literally what the intellij "Build Project" button is for.

Which you have to press. In default eclipse setting, it just happens without you having to press anything.