> Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat

> Dependencies between modules in the same source base for one, which given the most common setup (single workspace) Eclipse will quite happily ignore and treat everything as one module. Wait what? I have no idea what you are talking about. If modules are depending upon each other via Maven, you simply stick dependant one to the other's classpath if you want to use the workspace version. > The default static analysis setup misses so many common things (unused imports, methods, variables) that whenever I open a class in IntelliJ I have to spend 5 minutes removing the cruft. I'm looking at the same project here side by side and once again I'm not sure what you are referring to. If anything, some of IntelliJ assumptions for code quality can actually result in more fragile code if you aren't careful.