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.
Build #185 NBMs with NB6.1 RC2 MAC Mark reported a problem installing the 3 javascript debugger nbms that was solved by deleting the default dedicated userdir ~/.netbeans/6.1rc2 and restarting the IDE. The problem was reproduced on two other Mac machines. The symptom is that after the plugins are finished and the IDE is auto-restarted, the 3 nbms still can be found in the downloaded plugin manager tab rather than the installed tab. Sandip discovered two specific directories are involved -- that if the default 6.1RC2 var/cache and var/filehistory were removed, the plugins were recognized as installed. I repeated a fresh install of RC2 on the Mac to see if other plugins were affected by this but I was able to successfully install the VW compatibility kit and the Remove Unused bindings plugin with the default userdir OK. Seems to be our Javascript nbms. Other OS are fine with installing the Javascript Debugger NBMS. Sandip's initial assessment: Our modules have been added to the cluster.properties of jsdebugger repo only. May be that is the issue.
-Tested with 6.1 FCS bits on Mac - we still have this issue until, specifically, the all-modules.dat is removed from the default userdir .netbeans/var/cache. Thereafter the modules will appear in the installed plugins section and the debug property appears in project properties. (Interestingly, if the user happens to also install the VW1.4 plugin they avoid the issue and having to do the workaround.) -Also tested 6.1 FCS bits on WinXP - no issue.
Marked resolved/fixed in error. Undoing that. Apologies.
I have a theory: The <userdir>/var/cache/all-modules.dat of the NetBeans 6.1 RC2 after initial install is derived from the modules built by the nbbuild/cluster.properties in http://hg.netbeans.org/release61 repository. The JavaScript Debugger modules are not part of it. The JavaScript modules are built in the http://hg.netbeans.org/jsdebugger repository whose nbbuild/cluster.properties is aware of the JavaScript Debugger modules. We do not see the problem - for example - with Update Center installed VisualWeb Backward Compatibility modules because the nbbuild/cluster.properties in http://hg.netbeans.org/release61 repository is aware of those module. However the nbbuild/cluster.properties in http://hg.netbeans.org/release61 repository is not aware of the JavaScript Debugger modules (of course). The hacky work around could be to remove the <userdir>/var/cache/all-modules.dat when the module installation runs in the plugin manager.
It seems to be related to caching changes which were made couple of weeks ago by performance team in the code of core parts. Nevertheless I didn't catch the steps how to reproduce this issue. I do not know what is the build #185 and where can I obtain jsdebugger .nbms. Do you install modules via plugin manager's downloaded tab or did you also set up some update center? Please provide exact steps to reproduce so that we can evaluate. Thanks.
Hi, You can pick up "JavaScript Debugger" kit using this update center for now: http://blogs.sun.com/scblog/resource/jsdebugger/update-center.xml. You will see quickly that on the Mac after the restart the kit does not move into installed tab.
Fixed. Use a post install processing class to delete the userdir/var/cache/all-modules.dat file so that JavaScript Debugger modules will be installed after IDE restart. changeset: 78039:113dd1912db6 tag: tip user: Sandip V. Chitale <sandipchitale@netbeans.org> date: Sat Apr 26 16:02:50 2008 -0700 summary: Bug Fix # 133250 MAC - Plugins will not install with RC2 userdir; requires workaround
1. That is a workaround, not a fix. If the original problem can still be reproduced, I would urge you to file it properly, as already requested on nbdev. 2. You cannot have a Version of 6.5 and a Target Milestone of 6.1; it makes no sense.
Test failed on Mac Pro/Intel/Tiger/1.5.0_13 with NB6.1 FCS bits, NBMS http://blogs.sun.com/scblog/resource/jsdebugger/update-center.xml Plugin manager picked up bits for install, but on restart JavaScript Debugger was not found in installed panel. Found var/cache/all-modules.dat in userdir. Can send VNC coordinates if you want to take a look.
The bug was simply misfiled. Krys will fix that. Krys will file a separate bug against AU for describing the scenario. The AU developers were CCed on the bug so that they could provide some solution.
changing (error) version target; Also, I re-executed install, Sandip reminded me to check all-modules.dat both BEFORE and AFTER plugin forced restart. In both cases, I did not see jsdebugger plugin, but I *was* able to create a project and see the project Debug property. The modules did get installed - and they work - just no sign of it yet in plugin mgr or all-modules.dat until the first User restart (a minor issue). After user self-restart see debugger in Installed Plugin panel and all-modules.dat.
May be we can lower the priority. Krys, please capture all this for the other bug you will be filing.
Lowering priority as we saw this working already on several machines. Re-testing now on G5/PowerPc/Leopard.
I could not reproduce this after a couple of tries on the machine and never saw on any other Mac. Marking close and verified. The kit fix works around this successfully. I will file an autoupdate for our original issue.
Verified with latest bits 4/29/08 with 6.1 FCS.
Krystyna, please do file a bug to autoupdate. Thanks. We have reproducible case (on Mac only!) with JavaScript Debugger plugins if they don't include the workaround. We are still not sure where the reason for this problem is: seems either in Autoupdate code or somewhere in module loading.
I have filed issue #134395 to track the autoupdate issue which is the cause of problems with js-debugger installation.