<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"><div>I also be concerned
that existing releases of this frameworks/libs with dependences on
javax.security.cert.X509Certificate will be in use for some time.<br></div></blockquote><div><br></div><div>Based on my interaction with ecosystem projects so far, the prevalent sentiment seems to be "we plan to deal with this once OpenJDK removes the APIs". It seems this stalemate situation cannot really be broken before OpenJDK goes ahead with the removal. Providers like BouncyCastle and Conscrypt already have abstractions and build systems in place to handle these kinds of platform differences. They seem well equipped to handle this change.</div><div><br></div><div>Sure we can delay this a few releases, but I honestly don't see how that will materially change the situation. The band-aid that needs to be ripped at some point and the ecosystem seems to be waiting for OpenJDK to do so.</div><div><br></div><div>Thanks,</div><div>Eirik.</div></div></div>