You can ask IntelliJ to analyze your code and then it will tell you the places where a method could be static, for example. As far as I know the Java compiler d

You can ask IntelliJ to analyze your code and then it will tell you the places where a method could be static, for example. As far as I know the Java compiler doesn’t warn about this. So building the project will not tell you. Eclipse has a “problems” view which shows you all these kinds of problems across your whole workspace, all the time. I find that to be very nice: you configure Eclipse to show you the kinds of warnings you care about. Then you get a list of places to fix. And you can make sure that the list is empty at all times. In IntelliJ you have to start analysis, and the CPU fan spins up and it takes some minutes. And then the list of problems goes away after a while and you have to rerun analysis. In IntelliJ I make do with the annotations in the file I’m currently editing. IntelliJ also has smarter warnings than Eclipse does. But still, the problems view is very nice and I miss it.