----- Original Message -----
From: "Boleslaw Dawidowicz" <bdawidow(a)redhat.com>
To: "Stan Silvert" <ssilvert(a)redhat.com>
Cc: "Stian Thorgersen" <stian(a)redhat.com>, keycloak-dev(a)lists.jboss.org
Sent: Thursday, 26 March, 2015 7:32:48 AM
Subject: Re: [keycloak-dev] Java 8?
WildFly 10 is on what we'll need to align although it rather defines minimum
to support. Question is if we package with WF 10 which support only Java 8
will it be practical (and possible) to maintain compat with 7
That's what we need to align on for product yes, but other projects/products that
embed Keycloak need it to support whatever they support (BRMS for example doesn't even
start on Java8).
In summary we need to support Java 7 for a while longer :(
I would def keep 7 for adapters longer.
Dnia 25 mar 2015 o godz. 14:08 Stan Silvert <ssilvert(a)redhat.com> napisał(a):
>> On 3/25/2015 8:22 AM, Stian Thorgersen wrote:
>> That article doesn't make sense to me. Use Java8 for tests, but Java7 in
>> production, whaaat?
>> We need our testsuite to run on Java7, so can't take that approach.
> I could do it for Elytron tests since they only run under Java 8 anyway.
> For this discussion, I'm just trying to get a feel for when we might make
> the switch. I agree it may be a long way off for adapters.
> But I just got confirmation the WildFly 10 will require Java 8. If that's
> our target platform for productization maybe we should target Java 8 for
> the server side to coincide with that.
> Maybe Bolek has a better idea of the productization timing?
>> ----- Original Message -----
>>> From: "Stan Silvert" <ssilvert(a)redhat.com>
>>> To: "Stian Thorgersen" <stian(a)redhat.com>
>>> Cc: keycloak-dev(a)lists.jboss.org
>>> Sent: Wednesday, 25 March, 2015 1:11:44 PM
>>> Subject: Re: [keycloak-dev] Java 8?
>>>> On 3/25/2015 2:01 AM, Stian Thorgersen wrote:
>>>> It's to early for us to drop support for Java 7, especially for
>>>> The testsuite needs to run with both Java 7 and 8.
>>> Yea, I agree about that. Right now the only requirement is that the
>>> elytron tests require Java 8 at runtime. I don't need to actually use
>>> it from a source perspective.
>>> Aslak wrote a nice article on gradual migration of a project to Java 8.
>>>> I suggest we add a new module for those tests (testsuite/elytron) and
>>>> use a
>>>> Maven profile to run them only when the profile is active.
>>>> ----- Original Message -----
>>>>> From: "Stan Silvert" <ssilvert(a)redhat.com>
>>>>> To: keycloak-dev(a)lists.jboss.org
>>>>> Sent: Monday, 23 March, 2015 9:46:40 PM
>>>>> Subject: [keycloak-dev] Java 8?
>>>>> Java 7 is end of life next month. Elytron requires Java 8.
>>>>> Any opinion on when we should start using it? If I keep Elytron
>>>>> in the testsuite then the testsuite would need to run with Java 8.
>>>>> keycloak-dev mailing list