Hi Mark, My understanding is that JEP 161 (http://openjdk.java.net/jeps/161) already addresses many requirements for modularizing the Java runtime. JEP 161 should address the concerns around creating a scalable platform and improve performance.
I would like to understand what requirements in addition to JEP 161 this prototype aims to address. Best regards, David On 28 August 2013 17:27, <mark.reinh...@oracle.com> wrote: > I've created a new forest, http://hg.openjdk.java.net/jigsaw/jake, where > we're going to explore a simplified approach to achieving the goals of > this Project. To start, it's just a clone of the current JDK 8 master. > > Among other things, we're going to see whether we can get away without > introducing a distinct "module mode" as we have in the current prototype > (which is incompatible, in some narrow yet deep ways, with long-standing > behavior) and without doing dependence resolution (since build tools like > Maven, Ivy, and Gradle already do that well enough). > > We remain committed, of course, to this Project's high-level goals: > Create a modular and scalable platform, improve performance and security, > and define a standard module system. > > As we work on this new prototype we'll take code from the old one where > that makes sense, but we'll also take the opportunity to question earlier > design decisions and generally clean things up. > > I urge onlookers to remember that this is just another prototype. It is > likely to evolve swiftly. Its shape and content at any given point in > time should not be treated as having any particular bearing on the final > result of this Project. > > - Mark >
