-
Bug
-
Resolution: Unresolved
-
P4
-
9, 23
-
None
The module resolution and Configuration.resolve API docs do not specify anything on whether an automatic module reads modules in parent configurations. Right now, the implementation arranges for an automatic module to read all modules in the parent configurations but this is problematic when a parent configuration contains a module with the same name as a module in the candidate configuration, or where there are two or more modules with the same name in the parent configurations.
- relates to
-
JDK-8334761 Source launcher fails with "Module reads more than one module named" error
-
- In Progress
-