RFR: 8268573: Remove expired flags in JDK 19

[David Holmes]

On Wed, 15 Dec 2021 07:31:29 GMT, Alan Bateman <alanb at openjdk.org> wrote:

>> 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.
>
>> 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.
> 
> The roadmap is clear, no issue there. I'm just saying that aggressive removal of obsolete options that are used in important servers is a PITA for testing. It's important to be able to run as many existing applications as possible with the JDK 19 EA builds, we just make it harder when it requires digging into scripts and configuration to remove options that would prevent the VM from starting.

Sorry but unless there are issues filed to have those scripts updated then what you say will apply the same in 6 months time. And if there are issues filed then they should be fixed now. So I don't see any point in changing the roadmap.

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

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