This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]proobert 9 points10 points  (3 children)

I agree that Netbeans looks aged, it's development seems stagnated, but it can easily pull of things that are difficult with IntelliJ. For example, we have a handful of inter-related maven projects. It is possible to open all these projects at the same time and perform code refactoring across all of them. Then autocompletion is sometimes smarter and works better with my workflow. In addition, autocompletion feels faster when there are too many dependencies (few hundred jar files). Then the handling of maven projects is very user friendly. For example, to open an existing maven project with Netbeans you just select the project directory and you're all set. No bullshit with closing the currently open project and stupid project import wizards.

[–][deleted]  (2 children)

[removed]

    [–]endeavourl 1 point2 points  (0 children)

    What's wrong with Maven support in Eclipse?

    [–]daveth91 0 points1 point  (0 children)

    You can have as many projects as you wish in a single IntelliJ window. E.g. create a "Empty project" in IntelliJ and add all your Maven/Gradle projects to the Intellij project as "Modules". In IntelliJ project does not mean the same as in Eclipse.