Given that "automatic modules" are meant to be a migration path, I think refusing any legacy jar adds an unfortunate surprise to migrating. I understand the intent to throw FindException with regard to real modules (has module-info.class), but why apply the same restriction to *automatic* modules? I would like to know the design intent here. Is there a downside in carving out an exception (no pun) for automatic modules?
Cheers, Paul On Tue, Aug 2, 2016 at 11:51 AM, Jochen Theodorou <blackd...@gmx.org> wrote: > On 02.08.2016 15:19, Peter Levart wrote: > >> Hi, >> >> Top-package (unnamed package) classes can not be referenced from classes >> in named packages anyway, so they usually represent just reflective >> entry points (such as Main class with main() method). >> > > In Java that is you mean. The JVM does not care about the package as long > as the class can be found, nor does a class loader. It is a java compiler > restriction, an intended one, but only for those wanting to be a java > compiler. > > bye Jochen >
