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.
The UI spec has the "Modules" list in the Sources panel, yet the impl has it in the Libraries panel for some reason.
Ups, true indeed. Isn't this typo rather in the UI spec. I think that users would rather try to find this in the Libraries panel than in the Source panel. Since there is light pararelism with Single Module properties. Please Jesse consider this.
The UI spec is intentionally the way it is, since modules in a suite are not "libraries" the way classpath elements are - they are part of the "source" of the suite. At least to my mind. Jano, any opinion?
Jano, please note, that it is not really a big problem to move the list from Libraries(current) to the Source(UI) panel. So just really the UI/usability issue, not laziness or developer's time issue ;)
Hmm, looking at it more, I see we have a selection of platform modules as well, which is in the Build | Module List panel. This is what I think fits better into the Libraries panel. So, can we do the following...? * Move the current Modules list from the Libraries panel into the Sources panel. And label the list with "Suite Modules:" label. * Get rid of the Module List panel and move the tree table into the Libraries panel. And use "Platform Modules:" label with the tree table.
I think that makes a lot of sense. I will take that into account when updating the specs.
See new specs.
Fixed. BTW Jardo, this means that the Libraries panel is ready (free) for your Module List panel. See the UI spec. Checking in ui/customizer/Bundle.properties; 1.45 --> 1.46 Checking in ui/customizer/SuiteCustomizerLibraries.form; 1.5 --> 1.6 Checking in ui/customizer/SuiteCustomizerLibraries.java; 1.13 --> 1.14 Checking in ui/customizer/SuiteCustomizerSources.form; 1.1 --> 1.2 Checking in ui/customizer/SuiteCustomizerSources.java; 1.3 --> 1.4
v