Having used both NetBeans and IntellIJ, I greatly prefer NetBeans. What drove me up the wall with IntelliJ was the poor Maven integration. Maven projects are f

Having used both NetBeans and IntellIJ, I greatly prefer NetBeans. What drove me up the wall with IntelliJ was the poor Maven integration. Maven projects are first-class citizens of NetBeans, which means that NetBeans can read POM files as NetBeans project files. NetBeans generates a small supplemental file (nbactions.xml) to cover the few project-related things the POM doesn't store (such as the name of the default main class or the path to the JVM), and it duplicates no information. IntelliJ, on the other hand, uses its own project format exclusively, it duplicates everything, and the IntelliJ project file regularly falls out of sync with the POM and has to be re-synced, which can be a nightmare. At the company where we used IntelliJ, I ended up just using IntelliJ as an editor, and I did all my building by executing mvn on the command line (and we, as a company-wide thing, never ran projects in IntelliJ: we had special scripts for that). And the only reason I used IntelliJ there was because our coding standards were defined as an IntelliJ config file; if not for that, I would've just used NetBeans. IntelliJ might be a better editor than NetBeans, and that's debatable because NetBeans is also a really good editor, but I simply cannot stand using IntelliJ for anything other than editing, while NetBeans handles non-editing tasks beautifully.