Really irritated with Netbeans 6.8 Beta: suddenly there are plugins missing (SOA, XML Schema Editor and WSDL) and if you are not careful to uninstall existing instances of Glassfish V3 then NB throws exceptions when you activate the Java EE and Web module. Worse, NB then hangs.
On the missing plugins, you can get access to the missing XML Schema Editor plugin by adding a new update center:
- Name: NetBeans Dev
- URL: http://updates.netbeans.org/netbeans/updates/6.8/uc/m1/dev/catalog.xml.gz
But when I tried to install it from here, I got this error:
So this might be the reason they left it out of 6.8, but it would have been good to be warned and even better if a fix had been promised. My cynical side wonders whether this is some sort of stealthy de-scoping of ‘enterprise’ features, coinciding eerily with progress on the Oracle/Sun deal and a less then fulsome commitment from Oracle on the future of Netbeans. I do hope I’m wrong, but other folk clearly think that Oracle’s view of NB is ambivalent at best.
Meanwhile, back to more practical things Netbeans-related. Have you recently updated your JDK installation (to JDK 6 Update 17)? What happened when you next ran Netbeans? Did you see a dialog telling you NB couldn’t find the JDK?
Annoyingly, when Netbeans installs itself, it creates an entry in the netbeans.conf file (in C:\Program Files\NetBeans 6.7\etc or the equivalent path in your installation) containing the explicit JDK path, e.g.
# Default location of JDK, can be overridden by using –jdkhome <dir>:
netbeans_jdkhome="C:\Program Files\Java\jdk1.6.0_17"
It’s seems a small thing, but forcing a user to fix this by locating and manually editing a configuration file is desperately poor. As NB makes this check as it starts up, it should make more of an effort to detect alternative JDK installations, present the user with what it finds and offer to adjust the configuration for you. It wouldn’t be hard.
no comment untill now