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.
Product Version: NetBeans IDE Dev (Build 110207-8a008060e9a8) Java: 1.6.0_20; OpenJDK 64-Bit Server VM 19.0-b09 System: Linux version 2.6.35-25-generic running on amd64; UTF-8; en_US (nb) Summary: I'm not able to register into NB7.0 GF v2 because it's missing in Servers wizard. Steps to reproduce: 1, in daily build install GlassFish 1.0, 2.x plugin 2, invoke adding server -> in the list of offered servers is GF2 missing
Please attach the ide log. I need to see if there is a hint in there. Here is the test that I just did... pulled the web-main repo built the ide started the IDE with a clean userdir activated the java se and java ee features found the glassfish v1,v2.x plugin in the update ui and installed it went to the add server dialog and glassfish v2 was a visible choice I registered my v2.1.1 install i created an app that targets the registered v2.1.1 server I ran it it ran successfully. Can you provide a bit more detail about how you ran into this issue? Step by step instructions would be the most useful...
I tried a second strategy to trigger the issue, but could not.... Here is what I did: built a fresh pull of NetBeans from the web-main repo started it with a clean userdir Opened the Plugins dialog and installed the GF v1,v2.x plugin registered my GF 2.1.1 install I am going to need more info to replicate the issue and proceed...
A screenshot of the dialog may be helpful too.
Ok, I'm decreasing the priority. I found out that the issue is reproducible only with imported history from NB 6.9. It means, I'm not able to reproduce it with clean user dir. But I suppose that everybody is importing history from older Netbeanses to save his settings. Steps to reproduce: 1, build new IDE 2, start the IDE with new UD and click for importing history 3, install Glassfish plugin -> no GF v2 appears in Servers
Did you have an instance of v2.1 registered in the 6.9 setting that were imported?
No, I hadn't.
Another question... were the other historically available servers available... like SailFin, GlassFish v1 and SJSAS 8.2... even though GlassFish v2.x was 'missing'? Does the v2 choice appear in the dialog after a restart of the IDE?
Yes, right. There were available all another servers (GF 1, SUN App server, Salfin). Yes, the IDE restart helped.
*** Bug 196994 has been marked as a duplicate of this bug. ***
Restart helped for me to. But I consider this one as a P1 for NB 7.0. As stated in comment #4 this seems to happen only when importing settings from 6.9, which will likely be the case for most (if not all) users installing the final 7.0 version. Should be easily fixed/worked around though by setting "Needs Restart on Install" in the plugin properties...
Sorry mithridates lowering the priority a little bit - there is no data loss, serious memory leak etc. and the issue has quite simple workaround. Vince, as was mentioned, could you mark that plugin for requiring IDE restart?
(In reply to comment #11) > Sorry mithridates lowering the priority a little bit - there is no data loss, > serious memory leak etc. and the issue has quite simple workaround. Ok, no problem, as long as it gets fixed... ;-)
following the advice in http://netbeans.org/bugzilla/show_bug.cgi?id=195117#c10 to resolve this issue.
Integrated into 'main-golden', will be available in build *201103290400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/55b1d0f4d44b User: Vince Kraemer <vkraemer@netbeans.org> Log: #195117 : Force restart to prevent missing server registration choices
in dev build
*** Bug 197388 has been marked as a duplicate of this bug. ***
this change is in the 7.0.1 branch, as best I can tell. The GlassFish v1,v2 plugin needs to get rebuilt and placed in the UC so this change can get to users, though.
Cc'ing Petr G as the release engineer. Petr, this plugin is on the Certified Update Center. What needs to happen to refresh it on the UC? Thanks.
(In reply to comment #18) > What needs to happen to refresh it on the UC? Thanks. The fix has to be ported into the release70_fixes branch and the specification version has to be incremented for changed module(s). Once it is done I will run the 70fixes build and put the patch to staging.
in the releas70_fixes branch http://hg.netbeans.org/releases/rev/38a3187d862f
The fixed module has been uploaded to the stage AUC: http://updates.netbeans.org/netbeans/updates/7.0/uc/final/certified/catalog_stage.xml.gz Please, let me know once the download and installation of the module is tested.
Download and installation from staging works for me.
I guess correct target milestone is 7.0.1, please correct if I am wrong
The NBM has been moved to the certified 70 AUC.