On 26.05.2017 01:04, Alex Buckley wrote: [...]
The semantics of an observed JAR without module-info.class are specified as part of JPMS resolution, and JLS 7.3 explicitly defers to that, so I believe it is clear how a compiler must behave when a modular compilation unit 'requires' a module that turns out to be automatic. (Of course a big part of the migration story is that the requirer is unaware of whether the requiree is automatic or explicit.)
Isn't the consequence that I can write a compiler which does only allow named modules?
bye Jochen
