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.
Navigator is not part of the platform9 cluster. However, when the user uses the 'Window Component wizard', one of the available modes is 'navigator'. So the user registers a TopComponent in the 'navigator' mode even though the Navigator is potentially not part of the NetBeans Platform application, if it is using platform9 only. It would be good if the Navigator were to be part of platform9 because it is generally used throughout all NetBeans Platform applications, not NetBeans IDE or editors only.
Changed to enhancement request.
Added Adam Bien to cc.
It is a DEFECT if the mode is available when the module is not. The mode definition should be moved to the module that interprets it. Not sure I agree that this module needs to be pushed down into the platform cluster. If you want to use it from the ide cluster, you already can.
The mode isn't available (which is the problem, in my opinion) but I guess the problem from your perspective is that 'navigator' is mentioned in the drop-down list for Positions in the Window Component wizard, regardless of whether the Navigator module is available to the application. I think that would be an impossible condition for the Window Component wizard -- i.e., that entry would be added if amd only if the Navigator module will be in the final application. Therefore, I suppose the 'navigator' item needs to be removed from the Window Component wizard. (I would propose one single module that provides all the modes, regardless of whether their related window is included.)
"'navigator' is mentioned in the drop-down list for Positions in the Window Component wizard, regardless of whether the Navigator module is available to the application" - if true that is a bug in apisupport.project. "that would be an impossible condition for the Window Component wizard -- i.e., that entry would be added if amd only if the Navigator module will be in the final application" - I don't think so; various wizards already check the effective SFS according to the modules included in the suite, and present options accordingly. For example, when creating an action you are prompted to put it into menus that actually exist in platform (or other suite) modules.
I just checked in a dev build with a dev platform - made a new NB app, added a module, ran Window wizard, no navigator mode displayed.