Mandatary nature of standard Java SE modules

[Simonis, Volker]

Hi,

in a previous conversation (see below) I objected the wording in the "Goals" section which stated that "standard modules that are part of the Java SE Platform Specification" are "mandatory in every Platform Implementation". You agreed and removed that sentence from the latest 'public review' version of the specification.

While digging deeper into the specification, I found a similar phrase in subsection 4 of the "Design principles" section which states that "If a standard module is a Java SE module, i.e., is mandated by this Specification, then it must not export any non-SE API packages, at least not without qualification".

I think the subsentence ".. i.e., is mandated by this Specification .." should be removed because the specification doesn't mandate all Java SE modules.

Thank you and best regards,
Volker


> > That said, the "Goals" section also mentions that "standard modules
> > that are part of the Java SE Platform Specification, and thereby
> > mandatory in every Platform Implementation" which seems to contradict
> > with the above points which explicitly allow sub-setting (as long as
> > that set is closed).
> 
> That text is incorrect -- the "mandatory" clause should be removed.
> Thanks for catching this inconsistency.