Implied readability + layers

Alex Buckley alex.buckley at
Fri Nov 6 01:10:34 UTC 2015

On 11/5/2015 2:30 PM, Ali Ebrahimi wrote:
> On Fri, Nov 6, 2015 at 1:09 AM, Alex Buckley <alex.buckley at
> <mailto:alex.buckley at>> wrote:
>     A single version of in a program is strongly presumed to be
>     better than multiple versions of in a program.
> In Ideal world this would be perfect.
> But, If you use many modules from different third-parties with different
> release cycles, things may change and finding this single version may be
> impossible.

Disagree. Since JDK 1.0, people have been finding this single version by 
putting it earlier on the classpath than other versions. And if other 
versions have been shaded so as to co-exist on the classpath with the 
primary version, then that technique will still work in modules.

There is a requirement to support modules from different third parties: 
-- but that doesn't mean arbitrary combinations like a module in a child 
layer overriding a module in a parent layer.


More information about the jigsaw-dev mailing list