This might lead to worse API choices as it constraints us to not use new Java 8 features.
-----Original Message-----
From: Sergey Beryozkin [mailto:sberyozkin_at_talend.com]
Sent: Dienstag, 21. April 2015 12:59
To: jsr370-experts_at_jax-rs-spec.java.net
Subject: Re: JSR 370 Updated Schedule
Hi
As I've suggested earlier, it might make sense to start from working on JAX-RS 2.1 features that can still run with JDK 1.7 - simply to make the adoption of 2.1 faster for the existing JDK 1.7 users and get the features depending on Java 8 language features in the end/second half of the 2.1 development life-cycle. Not sure how realistic it is though
Sergey
On 13/04/15 20:42, Santiago Pericas-Geertsen wrote:
>
>> On Apr 13, 2015, at 1:21 PM, Markus KARG <markus_at_headcrashing.eu
>> <mailto:markus_at_headcrashing.eu>> wrote:
>>
>> Santiago,
>> can you please publish an updated schedule for JSR 370 as the
>> original scheduled apparently is void already. It says there is an
>> early draft in Q1/2015 and PR in Q3/2015, which apparently does not exist.
>
> I will, once I get a chance to review it with Marek.
>
>> Also I'd like to ask for clarification on Java 8: Will the new API
>> support Lambdas and Streams, hence make the use of Java SE 8 mandatory?
>
> Possibly. We certainly want to take advantage of SE 8 features, but
> we also feel that by the time EE 8 is out, SE 8 will be the mainstream
> version. As a data point, I believe Oracle will not provide any more
> public updates of SE 7 after this month.
>
> — Santiago
>