NetBeans roadmap (version 5.5)

So, while NetBeans 5.0 has only been out for a few days, Charles “demo-man” Beckham has already started the teasing on the future of Sun Java Tools on Intel-based Apple hardware. Of course, this is all plain Java, so it will run anywhere.

Looking closer at the snapshot, it seems that it boils down to the future of NetBeans. The NetBeans roadmap calls the next version 5.5.


The BPEL designer shown by Charles looks like what Sun Java Studio Enterprise TPR 1 (Technology Preview Release) has had for a few months now (the integrated BPEL engine will likely be different given Sun’s recent SeeBeyond acquisition and published roadmap).

The other big part of NetBeans 5.5 has to be Java EE 5 support (EJB 3, persistence API, JSF and dependency injection on both web and EJB tiers, JAX-WS 2.0). Daily NetBeans builds (no Q-build yet) have been available (choose “Java EE 5”) for some time now to use with GlassFish or JBoss. Several blogs entries on these have been written by Pavel, Martin, Petr, and Ludo.

If you’ve missed Gregg’s FAQ on Sun tools, make sure you read it.

Now, I still have (at least ;-) three questions: What about UML? Creator visual designer? When?

Author: alexismp

Google Developer Relations in Paris.

6 thoughts on “NetBeans roadmap (version 5.5)”

  1. ok, ok, I guess you’re asking for the future of NetBeans to be based on MevenIDE ;-)

    Once Maven 2 matures, that may happen, but I haven’t heard of such plans yet.

  2. re: Maven support.
    as a developer of Mevenide for netbeans, I would like to see maven part of the standard distribution. On the other hand I see problem that would arise.
    1. if both ant and maven are supported, you have to ask the user to make a decision what project to create. I’m pretty sure most users are not capable of making an informed decision. If you are asked questions you cannot answer, you get frustrated.
    2. Even if it may sound non-probable many users do struggle with Ant or see it for the first time in the IDE. While netbeans is capable of hiding the gory details of ant, I’m not sure it’s possible with maven. To name a few: dependencies, repositories, plugins.. these are the concepts that you need to be aware of before starting with maven (IMHO at least) How do you convince people that using the jars in their CVS is bad? without really going into the details?
    3. then there’s the relative popularity of ant versus maven. While I really do like maven and think it’s a better building tool, it’s not a popular belief (as of now)
    4. last but not least, there’s been a lot of investment by into the ant based project system and it probably wont go away any time soon.
    speaking for myself though, I’m not part of the decision making process at sun or
    Milos Kleint
    (on weekdays working for Sun on, on weekends on mevenide at

Comments are closed.

%d bloggers like this: