On 11.05.16 14:48, James Laskey wrote:
Wonder if we should have a configuration warning when an inappropriate version
is used.
+1, is it possible to implement?
Sent from my iPhone
On May 11, 2016, at 8:35 AM, Aleksey Shipilev <aleksey.shipi...@oracle.com>
wrote:
On 05/11/2016 02:28 PM, Alan Bateman wrote:
On 11/05/2016 12:14, Aleksey Shipilev wrote:
Got the same today, and figured it only fails with JDK 9 as the boot
JDK. Builds fine with JDK 8 as boot JDK. Filed:
https://bugs.openjdk.java.net/browse/JDK-8156740
You can never guarantee that the JDK N in development will build with a
older build of JDK N, there is just too much churn. Boot cycles builds
should be fine of course, meaning a JDK build should be able to build
itself (make bootcycle-images).
No problem with that. Let's close the bug with WNF and this description
then, so the next person facing this particular issue knows the
corrective action immediately.
Thanks,
-Aleksey
--
Best regards, Sergey.
