We should try to provide support for Java EE 8 streaming APIs or introduce reactive APIs, that may require CompletableFuture from Java SE 8. Also, we should try to make sure that our APIs are ready for lambdas.
Marek
On 20 Aug 2014, at 23:28, Bill Burke <bburke_at_redhat.com> wrote:
> What exact features are we going to take advantage of in Java 8? Is there really anything that compelling? I still have users on JDK 6.
>
> On 8/20/2014 4:40 PM, Santiago Pericas-Geertsen wrote:
>>
>> On Aug 20, 2014, at 4:26 PM, sberyozkin_at_talend.com wrote:
>>
>>> Hi Santiago
>>>
>>> I know Java 7 is not exactly new. But I'm sure you know many
>>> productions would not migrate to Java 8 tomorrow either.
>>> How exactly we'd look back by using Java 7 ? IMHO is not only about
>>> letting us play with excitement with new and cool features of Java 8.
>>> JAX-RS 2.0 is brilliant even without one or two Java 7 interfaces
>>> (AutoCloseable or whatever).
>>>
>>> This process is not about targeting the 'bleeding edge' productions
>>> where developers switch Java versions every month.
>>
>> I know, but 8 is not bleeding edge anymore, that's 9 now.
>>
>>> So we will look ahead and use the functional programming features or
>>> something even better of Java 8, that would super cool. Without those
>>> tricks 2.1 won't live I guess. Only part of the story though.
>>>
>>> Please give me a little time for me to confirm if I can be listed as a
>>> supporter, I'll get back on it asap.
>>>
>>> Also, let me ask, what is the targeted release date for 2.1 (sorry, not
>>> on my computer right now, no PDF reader here) ?
>>
>> Late 2016, and if history has taught us anything, that could mean early 2017.
>>
>> -- Santiago
>>
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com