Hi, I just opened a new thread for the Java 8 upgrade...
Thanks. Best regards, Jérôme 2016-07-25 15:26 GMT+02:00 larry mccay <[email protected]>: > Hi Jérôme - > > I think that we should start a DISCUSS thread on whether a Java 8 only > commitment would make sense as part of 0.10.0. > Since JDK 7 is already end-of-lifed this probably makes sense but we should > consider the rest of the ecosystem as well so that we don't leave anything > behind. > > This would also be relevant within a conversation for whether we should > plan a 1.0.0 release and what incompatible changes will need to be done > before hand. > > Perhaps, 0.10.0 should actually be 1.0.0 but we will need to address a few > things. > > I plan to cut a new rc for 0.9.1 today. > > Let's start this DISCUSS thread and JDK research across the ecosystem. > > thanks, > > --larry > > On Mon, Jul 25, 2016 at 6:33 AM, Jérôme LELEU <[email protected]> wrote: > > > Hi, > > > > In Knox, the CAS, OAuth, SAML and OpenID Connect authentications are done > > by the gateway-provider-security-pac4j module, which is based on > j2e-pac4j > > v1.2 and pac4j v1.8. > > > > Though, pac4j is now in version 1.9 and I just released the j2e-pac4j > > v1.3.1 (based on pac4j v1.9.1). > > > > As APIs have not changed much, the upgrade in Knox should be seamless, > > except that it now requires Java 8 while Knox is built with Java 7. > > > > Is the upgrade to Java 8 planned / possible and then the upgrade to pac4j > > v1.9 ? > > > > Thanks. > > Best regards, > > Jérôme > > >
