we cant do that simply.
Unfortunately we buld a custom KC server, based on 1.5 years APIs. we do
have a JIRA to decouple, so we can just point against latest of KC
On Mon, Jun 19, 2017 at 9:53 AM, Jose Miguel Gallas Olmedo <
jgallaso(a)redhat.com> wrote:
Does make sense to update Keycloak so it doesn't fail? It seems
to be a
dependency issue.
On 16 June 2017 at 13:16, Matthias Wessendorf <matzew(a)apache.org> wrote:
> just tested alpha1, but our legacy keycloak is biting us:
>
>
https://issues.jboss.org/browse/AGPUSH-2117
>
> -M
>
>
>
> On Fri, May 26, 2017 at 1:16 PM, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
>
>> Hi,
>>
>> while WF 11.0 is not yet release, I'd like to see us getting on to WF 11
>> on the master branch
>>
>>
http://wildfly.org/downloads/
>>
>> I think that our master branch should be exclusively target the latest
>> from WF stable, which is 11 in the future. So getting to know what's
>> problematic w/ the WF 11-alpha series is a good thing.
>>
>> Comments ?
>>
>> -Matthias
>>
>> --
>> Matthias Wessendorf
>>
>> blog:
http://matthiaswessendorf.wordpress.com/
>> twitter:
http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
JOSE MIGUEL GALLAS OLMEDO
ASSOCIATE QE, mobile
Red Hat
<
https://www.redhat.com/>
M: +34618488633 <
http://redhatemailsignature-marketing.itos.redhat.com/>
<
https://red.ht/sig>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev