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.
----- 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 adapters.
> 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.
https://gist.github.com/aslakknutsen/9648594
>
> 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 tests
>> in the testsuite then the testsuite would need to run with Java 8.
>>
>> Stan
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>