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 there is an implementation dependency on some module the user is not able to see all packages which may be used from that module. Since the list under "Include API Packages in Classpath" shows only public/friend packages. So for implementation dependency the list is often empty. Does it sound reasonable? If yes, then also the label should be changed to "Include Packages in Classpath", i.e. without API, since you always see the packages.
I guess the list should show only public packages normally, but if impl dep is selected, show all packages.
This is often confusing. TM -> 5.0u2.
test/unit/UtilTest.java; 1.21 -> 1.22; Util.java; 1.39 -> 1.40; ui/customizer/Bundle.properties; 1.79 -> 1.80; ui/customizer/EditDependencyPanel.java; 1.22 -> 1.23; ui/customizer/SingleModuleProperties.java; 1.61 -> 1.62; universe/AbstractEntryWithSources.java; 1.8 -> 1.9; universe/BinaryEntry.java; 1.9 -> 1.10; universe/ModuleEntry.java; 1.10 -> 1.11;
Partially fixed. Yes private packages are listed in package list when you select implementation dependency. IMHO user expects that the packages will be selected if you select implementation dependency.
They are included by default when you add a new dependency. So also when you then switch to implementation dependency. So they are not checked only on user's purpose. But probably does not make sense to have implementation dependency without compile dependency. ui/customizer/EditDependencyPanel.java 1.24 -> 1.25;