Results from NetBeans 6.1 Community Acceptance survey
Overall Quality comments
Definitely
JEE5 + Jboss 4.2 support is SORELY missed
There is a bug in the Woodstock Calendar component (I'm aware that Woodstock is a separate project, however, it is so tightly integrated with NetBeans that many developers will not be able to tell the difference). When placing the calendar component in a grid panel, it does not align properly with other JSF components in the panel. I think this is a serious issue since the standard way of aligning components in a form in JSF is to use a grid panel. The Woodstock issue can be found here. I did some "digging" and I think I have some information that might help the developers solve it, my comments can be found here.
releasing without fixing this issue would be a step backward.
Very much improved. Could not find groovy plug-in in the list of available plugins.
Mercurial support is - to be frank - pathetic! It should not have been integrated as standard feature at this stage. It gets confused, hangs and adds build/dist/private directories to version control at whim.
I can't wait for 6.1 to be released so I can use it in my professional projects.
I think 6.1 has a lot of improvements over 6.0. But for me one problem still exists, which is, after downloading (via maven plugin) all my libraries.. all sources are still marked as uncompilable. I have to manually open every one of them before netbeans notices that it can compile. I tried reload project without any luck
The selected in the properties of drop down list cannot be connected with a CachedRowSetDataProvider. The pop up of the selected does not show any CachedRowSetDataProvider. In 5.5.1 it worked fine. Without fix of this bug you cannt develop vwp application with 6.1 . This is a fact.
Still some bugs, however nothing serious to complain about.
issue while running on last Ubuntu, with any Java 6 at least.
I cant debug Web Projects from Enterprise project's Debug option
I've managed to manually work around this issue, but users in general will get mad if they lose their library settings...
NOT STABLE YET. - tried to rate not stable in this survey, but survey won't let me submit without a showstopper number. When I enter the issue number and submit it still doesn't like it... thus i have to submit as "some problems, but ok". Please read below... Numerous issues with UTF encoding problems in Web applications. I have tried several different Java web projects on two different installs of NB6.1RC1 and gotten similar errors pertaining JSP parsing exceptions, UTF8 encoding errors, and javax.swing.text.BadLocationExcetions (which occurred when I opened a web project and the NetBeans indexer was running). These same projects run well in NB5.5 and 6.0.1. #46516#46804 These issues make NB6.1 all but unusable for my web projects.
I don't know the bug numbers, but I don't think the IDE is ready for release. 1. IDE frequently forgets about some of my classes. They are not available from code completion, usages, refactoring, etc. The problem goes away for particular file, when I manually open it from the Files window. 2. due to p.1 (and possibly something else), IDE sometimes fails to correctly track the dependencies between classes and does not mark errors in files until I open them
Small regressions - the preferences dialog doesn't reflect changes in font for example. The IDE will use the correct font, but the preferences continue to show "monospaced" and the sample text remains courier. Also, the "scanning classpath" popups that happen when attempting to search or find usages - often it gets stuck and won't go away.
I can't use it until there is full Facelets support.
I get frequent (once per day) out of memory errors with memory suddenly filling up quickly and forcing me to kill the process. Lots of issues with rails in 6.0 hope they are fixed in 6.1
The Swing GUI editor has a lot of quirks. I find that with any non-trivial form that it messes up my layout more often than it helps me. I have to fight it a great deal and put everything back in place because when I place one control it often shoves the other controls way out of place (using GroupLayout). There are also issues where it paints "snap-to" guidelines in one place and then does something entirely different when you drop the component. I have filed a bug on that. The problems are so bad that I was very tempted to call them a showstopper.
It still suffers from the near-killer that doing something outside of the 'best practices' behavior usually silently fails or fails with misleading messages. This is fine for experienced development but terrible for inexperienced users evaluating it. Also, most modules need much better documentation (not just 'what methods do' but 'what they expect' since, again, not providing that usually fails silently or cryptically).
UI freezes randomly. No particular scenario to recreate it, but it happens frequently (after being in use for minutes or hours). This does not happen with 6.0 or 6.0.1.
The platform is almost unusable until #128582 is solved. Third party libraries cannot be used until #129772 is solved. Old projects created with the netbeans wizards cannot be imported until the package refactoring described in #131040 is revoked. Netbeans 6.1 may be usable as IDE but a usage as platform is not given. Please fix the bugs for people using netbeans as platform or library.
It's great if you include the fix for the java reformatting problem where a blank line is inserted after a line containing comments.
