NetBeans 6.1 Highlights

Now that the NetBeans IDE 6.0 is out, work has begun on version 6.1 (despite the roadmap showing 7.0 as the next version.) Version 6.1 is due for release by the end of April 2008 -- just in time for JavaOne. What's even better news is that the NetBeans team has released Patch 1 through the update center, and soon will release Patch 2. We no longer have to wait months or even a year to get bugs fixed. Now they are delivering bug fixes regularly while simultaneously working on the next release.

I read through the list of tickets for version 6.1 and think that this release will be as important as 6.0 because it brings many integrated features that mainstream Java developers expect in an IDE. Here is a list of highlights:

  • 123600 Add support for Spring Framework. Read one of several wiki pages on Spring support. Yes there is a 3rd party plugin but I get the impression that Sun wants to match the capabilities of competing IDEs.
  • 123601 Add support for Hibernate Framework. Read the wiki page for more details, especially the link to functional specifications. It says they want to match or beat what IntelliJ IDEA has for Hibernate support.
  • 122884 Deployment to WebSphere 6.0 and 6.1. I met a couple of consultants at JavaOne 2007 who told me they won't even look at NetBeans until they can use it with WebSphere. I've read that WebSphere has 50% of the commercial app server market -- that's a pretty significant user base that might look at NetBeans once it can work with WebSphere.
  • 118971 Support for Axis runtime. Even though I use the JAX-WS standard, most Java developers I meet use Axis or XFire for web services. He's another large group of developers that may look at NetBeans once it supports Axis.
  • 122887 Facelets support as a standard part of NetBeans. Facelets is very important to JSF developers and is being standardized in JSF 2.0. The plugin already exists, but is a side-project from one of the NetBeans developers and it only recently became available for NetBeans 6.0. I don't think it's available in the update center, you have to download it separately.
  • 122889 GWT support as a stable quality module (on the update center)
  • 122264 Fix JavaScript code completion to be comparable with competition.
  • 118953 TCP/SOAP Monitor in the IDE
  • 98853 Code completion for javadoc tags
  • 48427 Integrate Refactoring Undo with Editor Undo and Local History
  • (many tickets) It looks like Sun is putting a lot of effort into the PHP support to make it as good as the Ruby support.

I'm a bit concerned that some of these features (such as Spring and Hibernate support) are listed in the TBD plan instead of specific P1, P2 or P3. I really hope they can do these in time for 6.1.

Comments (12)

Comments:

It would be really cool to have really good Appfuse support in Netbeans. I am not completly sure what would be needed, but Spring and Hibernate support is a big step towards it. I would like to be able to add new beans and be able to work in Visual Web designer with the JSP or JSF pages.

Posted by Markus on January 08, 2008 at 09:15 AM EST #

How about Flex?

Posted by lg on January 08, 2008 at 03:07 PM EST #

Why Flex when there is a JavaFX?

Posted by Ivan on January 09, 2008 at 02:33 AM EST #

More important, what about Groovy?

Posted by AxiomShell on January 09, 2008 at 05:57 AM EST #

There's a Groovy and JavaFX Script plugin for NetBeans already, just like GWT, Facelets, Spring, Hibernate, etc. For NetBeans 6.1, Sun is taking a handful of these plugins and completing them or writing new plugins.

Posted by Ryan de Laplante on January 09, 2008 at 08:42 AM EST #

Wow, Netbeans has been improving by leaps and bounds! Every release since 4.0 has been excellent.

I used to love Eclipse (and still do) but Netbeans is much more integrated and this makes me far more productive with it.

Posted by Dimitris on January 10, 2008 at 03:35 AM EST #

I hope the JSF editor gets unshackled from Rave. I like it, but I really dislike the Rave-style backing beans. It should be a simple matter to make the editor simply update the JSP page and not muck with a backing bean. Also, I hope that there is an option to edit plain old standard JSP pages (not just webuisf).

Posted by Cay Horstmann on January 10, 2008 at 02:02 PM EST #

I talked with one of the main Visual Web Pack developers about these issues and wrote a blog entry about it. Yes they will be decoupling it from Rave and want to make it so you can use Seam, facelets, and other libraries. They also want to make the visual designer available for plain HTML and JSP editing. I don't know when that will happen though.

Posted by Ryan de Laplante on January 10, 2008 at 02:27 PM EST #

I hope one day NetBeans is going to implement back-ground compilation... A must-have feature for switching for my point of view. Another pleasure would be to see Jackpot project, an hidden jewel, promoted into official update centers, or event better, distributed with the IDE.

Posted by Dominique on January 10, 2008 at 03:59 PM EST #

Here are a couple links on ideas for 6.1 and 7.0:

http://wiki.netbeans.org/wiki/view/PostSixOhPerformanceTopics
http://wiki.netbeans.org/wiki/view/NB6WhatsNext

Posted by Ryan de Laplante on January 13, 2008 at 04:13 PM EST #

I'd like to see incremental/intelligent compilation - IntelliJ can build a few lines change in our prod system in seconds, where NB6 takes 2 minutes. Also with so many machines with 2, 4 or even 8 cores these days, how about parallel build support.

I'd like to see [J]Python get the same level of support as [J]Ruby.

I'd like to see support for Scala.

@Ivan - why flex? because you might already have a live, running flex-based app and want to work on it without the incredibly buggy eclipse-based ide that adobe provides. Having JavaFX support won't help you here at all.

Posted by Adrian on February 03, 2008 at 04:59 AM EST #

@Adrian
ur absolutely right ...

netbeans should get flex ... it would be awesome really awesome !!!

Posted by Sharique on February 04, 2008 at 07:59 AM EST #

Post a Comment:
Comments are closed for this entry.