java -modulepath

[Weijun Wang]

On Jun 25, 2011, at 12:28 AM, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> 
> One of the goals with this is to use it in the JDK build so that we can move away from the post-processing approach that we have in the jigsaw build now. To that end, both module and legacy modes have been updated to allow the JDK classes be in a module path structure. This should allow us to create the equivalent of the JDK's "make all" where the classes are compiled into a classes tree today, and a modules tree in the future. A "make images" builds the JDK image including rt.jar today, in the future it could create the modules image, installing the JDK modules into the module library. This will all require coordination with the other build changes going into jdk8 but a reasonable direction to take as it makes incremental building very simple and fast (and incremental builds are really important when working on the JDK).

I completely agree with this.

Every time Eclipse announced a new release, I would grab an installer to see how it feels. It never worked with "exploded" classes directory and complained java.lang.Object missing. Therefore, I've never been able to use any version for more than one hour.

-Max

> 
> 
> 
> -Alan.