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.
here I am referring Lookup.getDefault() as Default Lookup. this bug was found during my module development. But I am giving the different steps to reproduce this with netbeans IDE. Steps to reproduce: 1. have a fresh installation of netbeans IDE. here fresh installation I mean without any userdir. if userdir exists please delete that. 2. launch netbeans. create an AutoUpdateCenter from Tools->Options dialog. now open Tools->UpdateCenter dialog and you will find the newly created updated center listed there 3. close netbeans and launch it again. repeat the above step again. i.e, create an AutoUpdateCenter from Tools->Options dialog. now open Tools->UpdateCenter dialog and you will find the newly created updated center listed there 4. repeat the same step again. i.e, close netbeans and launch it again. create an AutoUpdateCenter from Tools->Options dialog. now open Tools->UpdateCenter dialog BUT, this time it won't list the newly created update center. i.e Default Lookup stopped working. now try adding more autoupdate centers or deleting existing autoupdate centers from Options dialog. but the UpdateCenter dialog will never update the dialog. I considered this as P1 bug. feel free to change the priority if requiried.
but If I create an FolderLookup on "Services" folder and use it instead of Lookup.getDefault(), then it is working fine. currently I am using this workaround instead of using Lookup.getDefault()
which version of the IDE you're are talking about? 3.6 final? or 4.0dev nightly?
netbeans 3.6 final
this is happening when the netbeans IDE is launched for 3rd time...
this is likely a duplicate of issue 44365. Yarda is on vacation. Petr N can you please evaluate this bug? Issue 44365 has been downgraded from P1 to P3. I think it must be P2 at least
Do you reinstall any module? If so, this would be duplicate of issue 44365. We have fix for it, but it is not tuned yet. Otherwise, I am not sure, but nobody is going to fix 3.6 bug soon anyway, so P1 won't help you at all.
but here I didn't install any new modules at all. I am able to reproduce this bug with fresh intallation.
I don't see even the second-added UC from the step 3. It runs fine with -J-Dnetbeans.cache.lookup=false, so the problem is obviously in the lookup cache. I'm closing it as duplicate of #44365. *** This issue has been marked as a duplicate of 44365 ***
verified