Skip to main content

What's the most significant new feature in NetBeans 6.7?

Integration with Project Kenai
5% (14 votes)
Native Maven support
31% (79 votes)
Hudson integration
4% (11 votes)
Language support enhancements
12% (31 votes)
GlassFish integration
5% (14 votes)
Other
7% (18 votes)
I don't use NetBeans
35% (90 votes)
Total votes: 257

Comments

Lack of JavaFX support

by swpalmer - 2009-07-17 05:30

JavaFX support would be nice. The fact that it is missing is a significant "feature".

Bad Groovy support

by trcorbin - 2009-07-15 06:48

The more I use groovy the more frustrating it is that netbeans support for groovy isn't that good (can't use 1.6.3, no fix imports, no refactoring, rarely working cc, etc.). It's also frustrating that there's no communication about it. For those reasons I'm looking to abandon netbeans.

None of the above

by vprise - 2009-07-13 10:33

All of the mentioned features aren't useful for me personally. So far I'm staying with 6.5.

None of the above

by prime21 - 2009-07-13 12:37

Ya. You don't want to pay those outrageous licensing fees to upgraded to 6.7... Oh, what? Netbeans is open-source. Oh. Well, then, I guess you'd be an idiot not to upgrade and get the improvements for free :-).

None of the above

by vprise - 2009-07-14 11:18

Since I was forced to upgrade to 6.5 stability in NB has decreased (compared to 6.1). I see no indication that 6.7 is stabler in the features I require. It will most likely be slower since it has MANY more features. Sure I can try to disable them one by one (as I did in 6.5) but why bother? Why download and install something you don't need? That would be...

Startup time

by carcassi - 2009-07-14 12:32

One of the other features NB 6.7 has is that it more or less automatically disables what you are not using... That alone was why I upgraded: the startup time was cut in half for me.

It also seems to be more clever in the initial scanning of the projects, which in NB 6.5 essentially froze my IDE for a few minutes before I could actually do anything relevant...

not idiot

by weeanon - 2009-07-13 12:55

hey, migrating the IDE to a new version in the middle of the project may introduce unnecessary risks, like changed behaviours (that will force the team to get used to them again), possibly greater hardware demand (we never know), discontinued features, incompatibilities with plugins, new bugs (every version of everything always fixes old bugs and brings us brand new ones), etc. what is idiot is migrating just because it is a new version. we have to test things first, and then see if they will come for better or not, considering the whole project situation, deadline, budget, etc. unless we want to play "developers and cowboys". amateur.