Alternatives for naming automatic modules, and a proposal (#AutomaticModuleNames)

[Michael Nascimento]

On Tue, Apr 25, 2017 at 10:10 AM, David M. Lloyd <david.lloyd at redhat.com>
wrote:

> Just the fact that there is the *very idea* of a "fit"/"non-fit" for JPMS
> is sad though.  It should have been the ubiquitous thing that everyone was
> expecting.  But denying multiple versions?  Blowing up on run time cycles?
> Reneging on the idea of being the basis of Java EE 9? These are things that
> people will not be expecting.


Some extra feedback: I delivered a talk yesterday at QCon SP and people
were very much disappointed with these limitations, and also the fact
packages must be defined by a single module even if they are not exported,
because it was considered nearly impossible to track in real world
scenarios.

Regards,
Michael