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.
Summary: | The IDE cannot install modules even though they are available in update/download directory. | ||
---|---|---|---|
Product: | platform | Reporter: | pgebauer <pgebauer> |
Component: | Autoupdate | Assignee: | Jaroslav Tulach <jtulach> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | blaha, ca-nb, dlipin, jtulach, mmirilovic, sustaining |
Priority: | P1 | Keywords: | RELNOTE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
messages.log
NBMs are available but the IDE doesn't know it. Set of logs from a different attempt. Set of logs from a different attempt. Set of logs from a different attempt. log 1 log 2 log 3 |
Description
pgebauer
2009-07-21 23:22:57 UTC
Created attachment 85041 [details]
messages.log
Created attachment 85042 [details]
NBMs are available but the IDE doesn't know it.
Upgrading the priority to P1. Is it reproducible if you install Java distro without ergonomics (Feature on Demand in installer customization panel/ dialog) ? Is it reproducible on Windows/Linux? Do you have "Force install into shared directories" checkbox enabled at Setting tab? Please attach all the messages.log* files (messages.log.1, messages.log.2), not only the latest. Created attachment 85053 [details]
Set of logs from a different attempt.
Created attachment 85054 [details]
Set of logs from a different attempt.
Created attachment 85055 [details]
Set of logs from a different attempt.
I'm sorry but I'm not avare of any Feature on Demand in installer customization panel/dialog on MacOS X. User blaha reproduced the issue on Linux, I guess. Hi Dima, we discussed that recently with Yarda ... - reproducible only for Java distro (not JavaSE) - after download feature : available in All IDE and not available in Java distro Dima, are you able to fix it ? We discussed that with Yarda recently (I thought you are on vacation) and he is willing to help us, but would live that on your shoulders if youy are back from vacation. ... and here is the NPE from updater while restarting the IDE: java.lang.NullPointerException at org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:833) at org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) at org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) at org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) The NPE is thrown while processing some Ruby NBMs: n: nb_autospec_loader.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: nb_autotest_loader.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: nb_rspec_mediator.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: nb_suite_runner.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: nb_test_mediator.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: nb_test_runner.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: plugin.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: rake java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) n: rake_tasks_info.rb n: sync-stdio.rb java.lang.NullPointerException org.netbeans.updater.UpdateTracking$Module.writeModulesConfig(UpdateTracking.java:835) org.netbeans.updater.UpdateTracking$Module.writeConfigModuleXMLIfMissing(UpdateTracking.java:695) org.netbeans.updater.ModuleUpdater.unpack(ModuleUpdater.java:434) org.netbeans.updater.ModuleUpdater.run(ModuleUpdater.java:131) There is a Ruby NBM that contains files in root of ruby2 cluster and this is causing the NPE. core-main#9f23832f7257 Fixed in trunk. Can be backported easily to release67_fixes by hg pull -r 9f23832f7257 http://hg.netbeans.org/core-main/ The fix has been ported into the release67_fixes repository. http://hg.netbeans.org/release67_fixes/rev/9f23832f7257 Integrated into 'main-golden', will be available in build *200907230201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/9f23832f7257 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #168937: Files in root of a cluster could cause NPE when regenerating config files Product Version: NetBeans IDE 6.7 (Build 200906241340) Java: 1.6.0_15; Java HotSpot(TM) Client VM 14.1-b02 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) The issue is reproducible with build 2009-07-23_02-33-46, catalog URL: http://smetiste.czech.sun.com/builds/netbeans/6.7.1/fcs/2009-07-23_02-33-46/uc/catalog.xml.gz as described in steps to reproduce. Message logs are attached Created attachment 85120 [details]
log 1
Created attachment 85121 [details]
log 2
Created attachment 85122 [details]
log 3
This is different issue because there is the problem with dependencies now, see message.log: Warning - could not install some modules: org.netbeans.modules.ruby.kit - The module org.netbeans.modules.ruby.debugger would also need to be installed. org.netbeans.modules.ruby.debugger - The module org.netbeans.spi.debugger.ui was requested in version >= 2.16.2 but only 2.16.1 was found. Petr G. would you look on that? Thanks, Petr Alex, would you write steps and also which distro, NB version and also UC catalog did you use? I followed these steps and didn't get any error message and the upgrade works fine: 1) install NB 6.7 Java All distro and start with new userdir 2) register this UC in IDE: http://smetiste.czech.sun.com/builds/netbeans/6.7.1/fcs/latest/uc/catalog.xml.gz 3) install updates. This steps is required because this bug is fixed in updater module and must be updated before next steps 4) go to available modules tab and choose C/C++, PHP and Ruby and install without any error dialogs. We need to find out what you did differently then me. Thanks If I don't skip the step "3) install updates.", the update will go smoothly. If I skip it, I will get errors regarding unavailability of new versions of some modules as it is mentioned above and I have to re-install the IDE. I'm afraid, we will not be able to do anything with that. I exactly followed the steps described by pgebauer with NB 6.7 'Java' distribution and did not install Auto Update UI and Auto Update Services. Looks like that was the key difference. On the other hand, nothing prevented me from choosing that way and some users can do the same. I understand your point but autoupdate module includes the fix that resolves the issue with Ruby module update. Only users who have JavaAll distro and want to add Ruby will face this issue. This bug is already in NB 6.7 and nobody reported this issue yet. The fix is resolved in new updater then you must install it in your IDE. Let's to summarize when the issue will happen: 1) user has NB 6.7 JavaAll and wants to add Ruby. Usually, when users see update notification then they upgrade their installation and after that the bug will be gone. I guess, just minimal percentage will ignore update and install Ruby before. 2) NB 6.7.1 JavaAll users will not encounter this problem Therefore, I would suggest to add item into RELEASE notes that describes what to do and release 6.7.1 with this. The bug is fixed. Verified with UC catalog http://smetiste.czech.sun.com/builds/netbeans/6.7.1/fcs/2009-07-23_02-33-46/uc/catalog.xml.gz |