Proposal: drop support for VS2017 in mainline

Magnus Ihse Bursie magnus.ihse.bursie at oracle.com
Tue Aug 30 15:14:18 UTC 2022


I think the time has come for us to drop support for VS2017. Some 
arguments for this:

* VS2017 was moved to "Mainstream End Date" by Microsoft in April, 2022 [1]

* VS2017 do not support C11 properly, which makes the fix for 
JDK-8292008 non-ideal [2]

* VS2017 do not support the new conformant preprocessor, which will 
likewise make JDK-8247283 only half-fixed [3]

* VS2017 required us to do ugly workarounds like JDK-8286459, which 
likely should be reverted once we get rid of it [4]

Is anyone tied to VS2017 and would reject a PR that removes support for 
VS2017, leaving only VS2019 and VS2022?

/Magnus

[1] https://docs.microsoft.com/en-us/lifecycle/products/visual-studio-2017

[2] https://github.com/openjdk/jdk/pull/10077

[3] https://bugs.openjdk.org/browse/JDK-8247283

[4] https://bugs.openjdk.org/browse/JDK-8286459




More information about the build-dev mailing list