On 03/08/2016 08:49, Paul Benedict wrote:
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 appl
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?
On 02.08.2016 14:47, Stephen Colebourne wrote:
today. The vast majority of libraries porting to Java 9 will have to
export all packages because nothing else will work. In virtually no
cases, is the end-user developer going to be changing the exported
packages of the libraries they depend on.
OK
On 02/08/16 18:12, Paul Benedict wrote:
> Correct me if wrong, but it seems there is no universal way to flag
> something as compiler/tool generated. My take away from Alex's comments
> is that ACC_SYNTHETIC is very much concerned with
> implicitness/explicitness... but why? I still don't understan
