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.
Me too, even for C++. Wish it had Dlang integration too.
One of the big differences with both NetBeans and Eclipse is that it's commercial software with nice non-paid offerings. But, for example, for my project Community Edition is not an alternative due to lack of JSP editing. NetBeans is great for editing JSP.
Other shortcomings of Community Edition are survivable. In my case this is Google App Engine support that with a lot of manual configuration can be made to run and debug in Community Edition.
Fadware with plugins. Plugins, upon plugins, upon plugins, upon plugins.
I mostly like Jetbrains, I just prefer Netbeans for the UX and Maven integration.
I was truly surprised by the code inspections (the "linter") and the depth of code analysis that it does. The first community edition would get stuck on some weird constructs from time to time, but every update improves upon it and I haven't seen the 2016 edition to have any issues with the weirdest code I have to maintain.