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.
It's not possible to create web project with glassfish v3. GFv3 is registered in IDE, but its not in combobox with available application servers. It worked on yesterday build so it had to be broken in last few commits.
pcw is out of the office this week.
what bits were you testing?
Actually I was in yesterday and made a number of changes, but thanks Vince. Tester: Are you certain you have the "glassfish.javaee" module installed (Named Glassfish V3 JavaEE Integration)? And that it is module version 0.1.2? I just tested the latest bits and V3 installs fine and shows up for web projects. Also what version of Glassfish V3 do you have? That might also make a difference -- the JavaEE facade has logic to detect the web container bits and will disable itself if they are not found. V3 is having some growing pains wrt/ naming and location of certain jars, so occasionally builds will fail this logic when the names change. (Maybe this behavior should be revised or removed).
well..i'm pretty sure. First i tried it on hg pulled netbeans - it already has module activated and then i tried netbeans installed using today installer. I have GF build 9. The same i used yesterday without these problems. I cannot check that glassfish.javaee has been installed right now . I've built nbm from contrib, but then i was surprised that built IDE (j2ee cluster) had already glassfish module in it. With installer IDE i'm more sure it was installed. But still not absolutely certain :). I will check it on Thursday.
No worries, I found out what it is, fixing it now
pcw: thanks for getting onto this. I am a bit lost on the new server vs. j2eeserver serverness...
Ludo updated paths last night to manage the SNAPSHOT vs TP2 naming changes that are forthcoming in future V3 builds. He forgot separating slashes in the changes to isModuleSupported() in the JavaEE facade factory, essentially disabling the JavaEE'ness of the plugin. I fixed it and bumped the module ID, so an updated module should show up on the dev update center soon. The Glassfish JavaEE Integration module must be version 0.1.3 for this fix.
pulled fix, rebuilt plugin and verified.