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.
When a fix was backported for openide-loaders module from 6.1 to 6.0 and the module was posted to (staging) update center after incrementing the spec number, the module could not be loaded by plugin manager, resulting in the following NPE: java.lang.NullPointerException at org.netbeans.modules.autoupdate.services.Utilities.findAffectedModules(Utilities.java:533) at org.netbeans.modules.autoupdate.services.Utilities.findRequiredUpdateElements(Utilities.java:605) at org.netbeans.modules.autoupdate.services.OperationValidator$InstallValidator.getRequiredElementsImpl(OperationValidator.java:152) at org.netbeans.modules.autoupdate.services.OperationValidator$UpdateValidator.getRequiredElementsImpl(OperationValidator.java:232) at org.netbeans.modules.autoupdate.services.OperationValidator.getRequiredElements(OperationValidator.java:118) at org.netbeans.modules.autoupdate.services.OperationContainerImpl$OperationInfoImpl.getRequiredElements(OperationContainerImpl.java:289) The above issue is most likely due to issue 122736 . The cause of the problem is that plugin manager "hits" the org.netbeans.modules.applemenu module during catalog.xml resolving. and the applemenu module is disabled and cannot be enabled (of course with exception of Mac computers). So there shouldn't be problem on Mac but all other OS... The fix is inside of autoupdate module and we are not able to deliver updates for autoupdate module; see issue 37133 which is fixed in NB6.1. Will later attach the nbm that led to this issue, for reproducing the issue.
Created attachment 56798 [details] The nbm that can be used to reproduce the NPE
The underlying problem, if fixed for 6.0 fixes branch, still cannot be delivered to 6.0 due to issue 37133. (37133 itself has been fixed for 6.1). Therefore marking this fix as wontfix. (It is not clear whether other core/openide modules also cannot be updated. But this problem can be re-visited if and when a show-stopper issue is found in any such module that leads to the NPE and this bug will need to be handled for 6.0. This issue has been created more for recording the issue than for resolving it; can always be reopened if it needs to be).