Five Favorite NetBeans IDE features

Thinking about it earlier today, I have been using NetBeans before (or after actually) it was called NetBeans.  I say after, because I remember using Forte but it was called NetBeans before and after Forte.  To put that into some perspective, some years ago I was at a JavaOne (2002?) at a Meet the Forte Tools Experts session.  NetBeans has come along way since those days but I recall seeing a lot of promise which has been a reality for a long time now.


  1. The first thing I liked, and still like, about NetBeans was that it has a familiar look.  This may be because I was a long time Delphi and JBuilder user, both Borland IDEs, and NetBeans was, at least to some extent, inspired by Delphi's IDE style and functionality.  NetBeans feels natural to me and I think it is generally very approachable for new developers.
  2. Out-of-the-box functionality is my second reason for liking NetBeans.  I install the full version of NetBeans on OS X, Linux, and Windows and I am up and running very quickly.  I use Subversion, Git,  and Maven and I do a variety of work in Java and this stuff just works.  
    Native alongside "effectively-native" maven projects
    It's worth pointing out that Maven support in NetBeans is not an afterthought or something that coexists as a native project type.  I can modify my pom file from within NetBeans or do a command line build and the IDE is in synch with the project because NetBeans "knows maven."
  3. No workspaces.  This may be unsettling for users of some other IDE's but I tend to want to open and close individual projects on demand.  I am usually involved in a variety of development efforts and I may need to open a project for a quick look or modification.  I also don't like the configuration bloat and potential corruption that may go along with the concept of a workspace.
    Close project in NetBeans - Out-of-Sight
  4. Code completion, hints, searching (across projects), and code generation.  These four are the tip of the iceberg for me.  
    NetBeans Code Generation
    They are the first four "I-know-the-IDE-is-smarter-than-I" features that don't get in my way and are available at the touch of a hot-key.  One very current example is if you're moving or thinking of moving a project to Java 8, give NetBeans a look and you will quickly understand what I mean.  I have used other IDE's that have similar features but I find myself just using them in NetBeans with no tweaking or searching.
  5. Open source community.  NetBeans itself is open as is the community.  While many folks may use software as is and wait for updates and new features, NetBeans users can have an active role in the development process.  Bug reporting, feature requests, testing, and support are all very active and welcoming communities and continue to make for a better IDE.
Happy coding,
Carl

Comments

Post a Comment

Popular posts from this blog

ClassCastException: JAXB

Image
A particular Java application I co-developed leverages both SOAP/WSDL and REST web services.  We use maven to manage the build process of this application which has been in production for a few years now.  It's been around long enough to have moved from Java 5 to Java 6 and now Java 7 (with limited testing using Java 8).  We have also had the experience of initially including JAXB jar files with our application and dealing with the "endorsed" directory because JAXB versions were a bit of a moving target for a while. Now that JAXB is neatly included with Java as it should be so we no longer include it.  I thought all of this was behind us (and unfortunately somewhat forgotten) until recently when we added Jersey 1.17 to the application to call some newer REST services. When trying to connect to the server, my stack trace included this: Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.internal.bin...
Read more

JDeveloper installation on Mac OS X Mountain Lion

Let's get the "why?" out of the way first - Personally I like to know what IDE's are alive and well for any for any Java development I might be doing especially if it's something new or something I have not done for a while. Currently NetBeans is my first choice.  Certainly Eclipse is a great standby for any Java development (and a whole lot of non-Java stuff for that matter).  I have tried to get into the in some circles extremely popular Intellij IDEA IDE but so far I am not a fan. JDeveloper , from Oracle, has an interesting history (I think back to my JBuilder days any time it's mentioned).  It still exists and I assume is well respected or at least used by those in Oracle shops because it does seem to integrate nicely with (or is at least aware of) all things Oracle. Recently I wanted to check out some functionality specific to JDeveloper and decided I needed to install it on a relatively new MacBook Pro running OS X 10.8.2 (aka Mountain Lion). ...
Read more

JNLP: note to self

Java security was a hot topic in 2013 and I think it will continue to get some attention as tooling catches up to the newer requirements.  Signing the JNLP for Java Web Start programs is now required. The Java Web Start maven plugin does not yet sign the JNLP file but there is an outstanding issue which I imagine will be resolved before too much longer. In the meantime, this blog entry  and this stack overflow question and answer  may be all you need to get your JNLP signed correctly. The way I read it, you have two choices. First you can create a template file which should be named APPLICATION_TEMPLATE.JNLP in src/main/resources/JNLP-INF and wildcards are permitted.  This is nice if you have the need to deploy your application from more than one server. The second method involves creating a file named APPLICATION.JNLP also in the src/main/resources/JNLP-INF folder.  This file must match the application's jnlp file exactly. Don't forget to mo...
Read more