> On Mar 23, 2018, at 7:51 AM, Stephen Colebourne <scolebou...@joda.org> wrote: > > Without being able to insist that a library is on > the module-path it is also clear that the benefits of strong > encapsulation and reliable configuration don't apply to library > consumers.
Why would a framework author ever want to cut off 99% of their users that are not using JPMS, most of which are completely happy with the arguably more flexible classpath? I think the only way you solve this problem is if you resurrect (and extend) some of the original goals to support common unification and bridging across runtime models. Then the industry as a whole could be pushing adoption. -Jason
