This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I just downloaded and installed the Glassfish V3-Prelude and NetBeans 6.7 Final (downloaded within 20 minutes of each other on 6/29/09) I then installed both on a clean machine (no ~/.netbeans folder) and NetBeans not recognizing the existing Glassfish servers on my machine (V2.1 and V3prelude [same as above] both downloaded and installed on 6/29/09). After installation, I went to the services folder and added the Glassfish V2.1 server successfully, but when I selected the Glassfish-V3 prelude folder, the system responded that ".../Glassfish-3p is not a valid GlassFish v3 Prelude installation."
which Linux? which URLs did you use to download v3 Prelude and 6.7 Final? I just tried it on my Solaris box... I downloaded NB 6.7 from here: http://download.netbeans.org/netbeans/6.7/final/bundles/netbeans-6.7-ml-java-solaris-x86.sh I downloaded v3 Prelude from here: http://download.java.net/glassfish/v3-prelude/release/glassfish-v3-prelude-ml.zip I was able to register the server just fine.
Also tested against 'installed' bits from http://download.java.net/glassfish/v3-prelude/release/glassfish-v3-prelude-unix-ml.sh. It looks like I need to get more info from you about the particulars of your environment.
Ubuntu 9.10 Jdk 1.6.0 u14
I downloaded Glassfish V3 Prelude directly from the Glassfish site (http://download.java.net/glassfish/v3-preview/release/glassfish-v3-preview.zip) this afternoon. It's different from the version you downloaded (http://download.java.net/glassfish/v3-prelude/release/glassfish-v3-prelude-ml.zip) so that may be part of the problem. Which is the newer version?
You downloaded v3 Preview... which is newer. NB 6.7 does not support v3 Preview... without the use of an enabler: http://blogs.sun.com/vkraemer/entry/experimental_features_marker If you want to use v3 Preview and recent v3 builds in NB, you can also download NB 6.8 nightlies... I am marking this as fixed. Please reopen if there is a problem using the enabler.