Geertjan's Blog

  • February 27, 2015

From Eclipse to NetBeans

Geertjan Wielenga
Product Manager

It's kind of hard to tell the difference between the snippets of code below. But they come from two different tools, one of them is NetBeans and the other is Eclipse. I think it's irrelevant to say which is which since the rendering of the font of each is excellent. I'd happily work with font rendered by either of the two different tools below.

By default, the coloring, and other styling, of font in NetBeans looks different to how it looks in Eclipse. That's easy to solve, assuming you find this to be a problem, via this excellent addition to NetBeans:


When switching from Eclipse to NetBeans, it certainly helps a lot if the project you're migrating uses Maven as its build system. Maven-based projects are automatically recognized by NetBeans. NetBeans understands that if a folder contains a 'pom.xml' file, it is a Maven project. Hence there's no import process needed. Instead, you can simply go to File | Open Project to open any folder containing a 'pom.xml' file into NetBeans as a Maven project.

Finally, you'll find this very useful, thanks to Benno Markiewicz, which lets you import Eclipse formatting files into NetBeans and use them to format your files:


Join the discussion

Comments ( 2 )
  • psychollek Monday, March 2, 2015

    unfortunately eclipse code formatter plugin doesn't preserve line breakpoints - lack of feature which makes spending about 10 minutes (tuning is really easy due to instant preview in configuration window) to tune netbeans code formatter like you had your eclipse formatter tuned, really worthwhile.

    OTOH I do use netbeans in company where ~97% of people use eclipse and don't have any problems with it (maven build).

  • guest Monday, March 2, 2015

    It is not the tool that works with the developer. It is the developer that uses the tool. Be it eclipse or netbeans, it really doesn't matter. It's time people let go with this eclipse vs netbeans.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.