On 2018-03-21 23:10, Magnus Ihse Bursie wrote:
Jon,
21 mars 2018 kl. 23:20 skrev Jonathan Gibbons <jonathan.gibb...@oracle.com>:
Holding javac and related tools back to the latest LTS would indeed be somewhat
onerous.
Can we use the interim JDK build to get around this? Something like, if we can
build a interim JDK with somewhat older tools, it can then be used to compile
the javac proper?
No, I can't see how that could work for simplifying anything here.
/Erik
I can see that how with the increased release cadence, the assumptions behind
the old N-1 scheme might not be valid anymore.
/Magnus
-- Jon
On 03/21/2018 03:07 PM, Martin Buchholz wrote:
Now that we are releasing jdks an order of magnitude faster than before, we
should reconsider the N-1 boot jdk policy.
The primary beneficiaries of this are compiler-dev, who might like to code
using the very features they are implementing.
But for users, being able to bootstrap with an ancient jdk is definitely
convenient.
A good compromise might be to be able to bootstrap with the most recent LTS
release (jdk 8) but it might already be too late for that.
On Wed, Mar 21, 2018 at 2:51 PM, Erik Joelsson <erik.joels...@oracle.com>
wrote:
Now that JDK 10 has been officially released we can update the boot jdk
requirement for JDK 11. Cross posting this to jdk-dev to raise awareness of
this rather disruptive change.
This patch changes the requirement on boot jdk version in configure (and
updates the configuration that controls what JDK to use as boot in Oracle's
internal build system).
Webrev: http://cr.openjdk.java.net/~erikj/8200083/webrev.01/
Bug: https://bugs.openjdk.java.net/browse/JDK-8200083
/Erik
