RFR: 8268573: Remove expired flags in JDK 19

David Holmes dholmes at openjdk.java.net
Wed Dec 15 00:18:58 UTC 2021


On Tue, 14 Dec 2021 13:11:26 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> I don't understand the relevance of "uptake of JDK 17" - this change only affects 19. Anyone on 17 will get the deprecation warning as we deliberately deferred obsoleting the flag until JDK 18.
>
> It means the start scripts won't be usable with JDK 19+ builds so it complicates testing with those servers. Once these servers get to JDK 17 (actually JDK 15+) then they should be able to drop this option. I think the more general point is that we could be less aggressive about removing obsolete VM options when we know they are being used. In the past, the PermGen options were left as obsolete options for a long time because there were widely used.

The roadmap for the deprecation, obsoletion and expiration(removal) of UseBiasedLocking has already been extensively discussed and agreed upon - ref JDK-8256253. Anyone who decides they want to try JDK 19 and have not yet updated a startup script will now be forced to do so - I don't see that as a bad thing. Anyone who has been ignoring the obsoletion warning in 18 testing is just as likely to keep ignoring it in 19 so I don't think we need to keep kicking this can down the road.

-------------

PR: https://git.openjdk.java.net/jdk/pull/6819


More information about the hotspot-runtime-dev mailing list