storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jungtaek Lim <kabh...@gmail.com>
Subject Fwd: [Discussion] Dropping Java 7 support on master
Date Fri, 12 Aug 2016 09:41:37 GMT
I was mistaken the address of user mailing list. Forwarding this to user@.

---------- Forwarded message ---------
From: Jungtaek Lim <kabhwan@gmail.com>
Date: 2016년 8월 12일 (금) 오후 6:38
Subject: Re: [Discussion] Dropping Java 7 support on master
To: <dev@storm.apache.org>, <users@storm.apache.org>


I'm not sure we would like to continue discussion on cross mailing list.
Please let me know if we want to split discussion into two separate thread
per mailing list.

I'm +1 on dropping Java 7 support on master (2.0.0).

While porting clojure code to java 7, we needed to convert functional style
functions to for loop which is too verbose and hide intention. It also
drops productivity.
We can do similar style by using Guava but it's more verbose, and Guava is
one of libraries I don't want to add as dependency. (Not only storm-core,
but also other modules.)

I'm not sure how much users are forced to not use Java 8. (This is common
concern of upgrading JDK version.)
At now, Java 8 is over than 2 years ago, and Oracle drop public support of
JDK/JRE 7 1 year ago. Furthermore, Java 9 will be released to next year.
(actually planned to this year)

I'm also the one who need to take a deep look at Java 8, but I think the
time has come. Let's go for that.

Thanks,
Jungtaek Lim (HeartSaVioR)


2016년 8월 12일 (금) 오후 6:10, Harsha Chintalapani <storm@harsha.io>님이 작성:

> Hi All,
>       Dropping java 7 support on master will allow us to use the new api in
> Java 8 and since the master is being used for java migration its good to
> make the decision now. Let me know your thoughts.
>
> Thanks,
> Harsha
>

Mime
View raw message