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.
While reviewing the NetBeans Platform Runtime Container Tutorial, I followed the steps to create a minimun app, selecting only the Startup package and the hitting resolve. Instead of 6 basic modules the resolve selected 9 modules. but then while running, an additional one (util.ui) was turned on even though it was not even selected in the Properties > Libraries, Platform Modules section: INFO [org.netbeans.core.startup.NbEvents]: Turning on modules: org.openide.util.lookup [8.33 201608150002] org.openide.util [9.7 201608150002] org.openide.util.ui [9.6 201608150002] org.openide.modules [7.48 201608150002] org.openide.filesystems [9.10 201608150002] org.openide.filesystems.compat8 [9.9 201608150002] org.netbeans.libs.asm [5.3 201608150002] org.netbeans.core.startup.base [1.62.0.1 1 201608150002] org.netbeans.bootstrap/1 [2.76 201608150002] org.netbeans.core.startup/1 [1.62.0.1 201608150002] com.aleph5.hellomodule [1.0 160816] I can understand that maybe new dependencies and changes can justify the increased number of minimum packages, but what is strange is to have an additional module being turned ob when it was not selected.
org.openide.util.ui dependency is introduced by the module system -- ModuleInstall extends SharedClassObject, which is a deprecated base class. We did not get rid of it during UI/backend split effort back in NB-8.0. The base class could be eventually changed, and a compatibility supplemental module can be provided which bytecode-injects a baseclass (extending SharedClassObject) in the case dependency on older spec version is found.
Closing.