On 17/03/2017 14:16, David M. Lloyd wrote:
Hmm, so automatic modules explicitly are going to allow cycles then?
How is that going to not hinder migration, if cycles are disallowed
once the thing is properly modularized?
Automatic modules are for libraries that have not been migrated. The
maintainers have to fix their issues as part of migration. When a module
declaration is synthesized for an automatic module then it only requires
java.base so it can't be involved in a cycle in the dependency graph.
-Alan
