<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The changes in JDK-8241047 were intended
to allow SSLSession implementations drop their dependence on
javax.security.cert.X509Certificate but it may take time if
implementations are still expecting to be able to compile to a wide
range of releases that include JDK 14 or older. </blockquote><div><br></div><div>JDK-8241047 was indeed a very good move, and seems to be a key enabler for projects to easily drop their dependencies on javax.security.cert. It is really unfortunate we missed the train on backporting this to the 11 MR.<br></div><div><br></div><div>I understand the concerns regarding implementations expecting to be able to compile to a wide range of releases. However, if we indefinitely continue to meet this expectation, then when can we ever remove anything? Besides that, BouncyCastle provides an example that it is very possible to move forward while still compiling to a wide range of releases - it just puts a burden on projects needing this to maintain a more complex build and release system.</div><div><br></div><div>Cheers,</div><div>Eirik.</div></div></div>