You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Harsha Chintalapani <st...@harsha.io> on 2016/08/11 21:24:19 UTC
[Discussion] Dropping Java 7 support on master
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
Re: [Discussion] Dropping Java 7 support on master
Posted by Harsha Chintalapani <st...@harsha.io>.
Jira and patch avialable here
https://issues.apache.org/jira/browse/STORM-2041.
On Fri, Aug 12, 2016 at 8:05 AM Harsha Chintalapani <st...@harsha.io> wrote:
> sorry for the multiple emails. Something went wrong on my email provider
> side.
>
> Instead of splitting into two separate threads as its hard keep track of
> the discussion. We can continue this discussion on users list as it will
> keep the storm users in the discussion as well.
> Thanks,
> Harsha
>
>
> On Fri, Aug 12, 2016 at 2:55 AM Satish Duggana <sa...@gmail.com>
> wrote:
>
>> +1 on moving to Java 8 for 2.x release.
>>
>> As Jungtaek has already mentioned Oracle stopped supporting JDK/JRE 7
>> since April 2015. Java 8 brings better APIs and it will make our code look
>> better and future user APIs can be designed lot better.
>>
>> Thanks,
>> Satish.
>>
>>
>> On Fri, Aug 12, 2016 at 3:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>>
>>> I was mistaken the address of user mailing list. Forwarding this to user@
>>> .
>>>
>>> ---------- Forwarded message ---------
>>> From: Jungtaek Lim <ka...@gmail.com>
>>> Date: 2016년 8월 12일 (금) 오후 6:38
>>> Subject: Re: [Discussion] Dropping Java 7 support on master
>>> To: <de...@storm.apache.org>, <us...@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 <st...@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
>>>>
>>>
>>
Re: [Discussion] Dropping Java 7 support on master
Posted by Harsha Chintalapani <st...@harsha.io>.
sorry for the multiple emails. Something went wrong on my email provider
side.
Instead of splitting into two separate threads as its hard keep track of
the discussion. We can continue this discussion on users list as it will
keep the storm users in the discussion as well.
Thanks,
Harsha
On Fri, Aug 12, 2016 at 2:55 AM Satish Duggana <sa...@gmail.com>
wrote:
> +1 on moving to Java 8 for 2.x release.
>
> As Jungtaek has already mentioned Oracle stopped supporting JDK/JRE 7
> since April 2015. Java 8 brings better APIs and it will make our code look
> better and future user APIs can be designed lot better.
>
> Thanks,
> Satish.
>
>
> On Fri, Aug 12, 2016 at 3:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>
>> I was mistaken the address of user mailing list. Forwarding this to user@
>> .
>>
>> ---------- Forwarded message ---------
>> From: Jungtaek Lim <ka...@gmail.com>
>> Date: 2016년 8월 12일 (금) 오후 6:38
>> Subject: Re: [Discussion] Dropping Java 7 support on master
>> To: <de...@storm.apache.org>, <us...@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 <st...@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
>>>
>>
>
Re: [Discussion] Dropping Java 7 support on master
Posted by Andrew Xor <an...@gmail.com>.
I concur; staying 1 major GA version behind is a nice idea. There's a limit
to what needs to be sacrificed for legacy support...
Cheers,
A.
On Fri, Aug 12, 2016 at 5:31 PM, Bobby Evans <ev...@yahoo-inc.com> wrote:
> +1 for me too.
>
> Java 9 is already in early access and is supposed to be GA fairly soon. I
> think the last time we talked about this we decided that staying 1 release
> of java behind the latest was decent practice, and I still agree.
>
> - Bobby
>
>
> On Friday, August 12, 2016 4:56 AM, Satish Duggana <
> satish.duggana@gmail.com> wrote:
>
>
> +1 on moving to Java 8 for 2.x release.
>
> As Jungtaek has already mentioned Oracle stopped supporting JDK/JRE 7
> since April 2015. Java 8 brings better APIs and it will make our code look
> better and future user APIs can be designed lot better.
>
> Thanks,
> Satish.
>
>
> On Fri, Aug 12, 2016 at 3:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:
>
> I was mistaken the address of user mailing list. Forwarding this to user@.
>
> ---------- Forwarded message ---------
> From: Jungtaek Lim <ka...@gmail.com>
> Date: 2016년 8월 12일 (금) 오후 6:38
> Subject: Re: [Discussion] Dropping Java 7 support on master
> To: <de...@storm.apache.org>, <us...@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 <st...@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
>
>
>
>
>
Re: [Discussion] Dropping Java 7 support on master
Posted by Bobby Evans <ev...@yahoo-inc.com>.
+1 for me too.
Java 9 is already in early access and is supposed to be GA fairly soon. I think the last time we talked about this we decided that staying 1 release of java behind the latest was decent practice, and I still agree. - Bobby
On Friday, August 12, 2016 4:56 AM, Satish Duggana <sa...@gmail.com> wrote:
+1 on moving to Java 8 for 2.x release.
As Jungtaek has already mentioned Oracle stopped supporting JDK/JRE 7 since April 2015. Java 8 brings better APIs and it will make our code look better and future user APIs can be designed lot better.
Thanks,Satish.
On Fri, Aug 12, 2016 at 3:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:
I was mistaken the address of user mailing list. Forwarding this to user@.
---------- Forwarded message ---------
From: Jungtaek Lim <ka...@gmail.com>
Date: 2016년 8월 12일 (금) 오후 6:38
Subject: Re: [Discussion] Dropping Java 7 support on master
To: <de...@storm.apache.org>, <us...@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 <st...@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
Re: [Discussion] Dropping Java 7 support on master
Posted by Satish Duggana <sa...@gmail.com>.
+1 on moving to Java 8 for 2.x release.
As Jungtaek has already mentioned Oracle stopped supporting JDK/JRE 7 since
April 2015. Java 8 brings better APIs and it will make our code look better
and future user APIs can be designed lot better.
Thanks,
Satish.
On Fri, Aug 12, 2016 at 3:11 PM, Jungtaek Lim <ka...@gmail.com> wrote:
> I was mistaken the address of user mailing list. Forwarding this to user@.
>
> ---------- Forwarded message ---------
> From: Jungtaek Lim <ka...@gmail.com>
> Date: 2016년 8월 12일 (금) 오후 6:38
> Subject: Re: [Discussion] Dropping Java 7 support on master
> To: <de...@storm.apache.org>, <us...@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 <st...@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
>>
>
Fwd: [Discussion] Dropping Java 7 support on master
Posted by Jungtaek Lim <ka...@gmail.com>.
I was mistaken the address of user mailing list. Forwarding this to user@.
---------- Forwarded message ---------
From: Jungtaek Lim <ka...@gmail.com>
Date: 2016년 8월 12일 (금) 오후 6:38
Subject: Re: [Discussion] Dropping Java 7 support on master
To: <de...@storm.apache.org>, <us...@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 <st...@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
>
Re: [Discussion] Dropping Java 7 support on master
Posted by Jungtaek Lim <ka...@gmail.com>.
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 <st...@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
>