On 24/04/2016 21:00, Paul Bakker wrote:
So when modules B, C and D are automatic modules and named module A depends on B, A also gets implicit readability to C and D? What is the reasoning behind this automatic implicit readability? It makes migration less reliable I think, because it hides what dependencies a module really has.I do see one issue with javac in that it is granting implicit readability to explicit modules too, that seems to be a bug because such code will fail at runtime.
-Alan
