When will JDK 9 builds move to requiring the boot JDK be JDK 8?

Martin Buchholz martinrb at google.com
Thu Apr 3 18:51:56 UTC 2014

On Thu, Apr 3, 2014 at 10:01 AM, Joe Darcy <joe.darcy at oracle.com> wrote:

>  On 04/03/2014 09:33 AM, Martin Buchholz wrote:
> On Thu, Apr 3, 2014 at 8:53 AM, Joe Darcy <joe.darcy at oracle.com> wrote:
>> A broader question this issue raises is why are components like corba
>> built using the book JDK rather than the JDK they are a part of?
>  If we're cross-compiling, the JDK being built may never be executable
> But the code in the jdk repository in JDK N is built such that it can use
> the language features and new libraries of JDK N. In contrast, the code in
> the corba (and IIRC jaxp and jaxws) repo is restricted to using features in
> the boot JDK, typically JDK (N-1).

No problem.  Java and bytecode are both architecture-independent, and
langtools can be compiled and run using JDK N-1, so: compile JDK N
langtools using JDK N-1 langtools, then compile the rest of the JDK using
JRE N-1 executing JDK N langtools as "Just another portable Java program".

Except for the small problem of collisions between javac.jar and rt.jar,
e.g. SourceVersion that Liam is trying to find a solution for (not
involving -Xbootclasspath/p:)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/compiler-dev/attachments/20140403/9c5dcab7/attachment.html>

More information about the compiler-dev mailing list