Going for it and releasing 3.3.0.Final soon.
With regards to Elytron API changes we'll just adopt those for 3.4. I
assume KC 3.3 Elytron adapters won't work with WF 11 FInal then, but we're
probably going to wait for WF 11 Final to release 3.4 anyways and we can
sort that out then.
On 17 October 2017 at 14:09, Pedro Igor Silva <psilva(a)redhat.com> wrote:
I think we can do that for this particular version.
But there are some discussions around some very specific changes to
Elytron's HTTP API that can impact our Elytron adapters. After talking with
Darran, these changes should not have a huge impact to our code but will
require some changes and a round of tests to make sure it is still working
as expected.
Maybe you should forward this e-mail to jboss-as list and gather more
feedback about any change that may impact future releases.
On Mon, Oct 16, 2017 at 11:19 AM, Stian Thorgersen <sthorger(a)redhat.com>
wrote:
> Still no WildFly 11 Final and it may be weeks until it is out.
>
> Question - should we just release Keycloak 3.3.0.Final based on WildFly 11
> CR1?
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>