[jboss-jira] [JBoss JIRA] (WFLY-13256) Upgrade bouncycastle to 1.65.0

[ https://issues.redhat.com/browse/WFLY-13256?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13256: ----------------------------------------- [~jim.ma] [~aabdelsa] Any PicketLink relationship is interesting. At some point, probably WF 22 if not before, I see us dropping the PicketLink subsystem from WildFly, as the community project is archived. I actually did a quick branch to do that -- https://github.com/bstansberry/wildfly/commits/drop-plink. (It's out of date now; would need a rebase.) To the extent any problem with this upgrade on JDK 13 is limited to PicketLink scenarios, my concern about doing it is reduced a lot. I try to use careful language when describing WildFly's support for JDKs after 11, e.g. from https://wildfly.org/news/2019/10/03/WildFly18-Final-Released/ {quote} Our goal with WildFly is to have our releases run well for most use cases on the most recent GA JDK version available on the WildFly final release date. I’m pleased to report that this is the case with WildFly 18 and JDK 13. By run well, I mean the main WildFly testsuite runs with no more than a few failures in areas not expected to be commonly used. We want developers who are trying to evaluate what the latest JVM means for their applications to be able to look to WildFly as a useful development platform. {quote} Problems due to use of PicketLink fall into the "not expected to be commonly used" area IMHO. Please note though that I don't want to ignore a broader problem that might affect lots of use cases beyond PicketLink. But if it is a PicketLink problem that would be very good to know. -- This message was sent by Atlassian Jira (v7.13.8#713008)