Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Rohit Yadav
compatible. [1] https://github.com/rhtyd/cloudstack-nonoss/blob/master/install-non-oss.sh#L20 Regards. From: Sudhansu Sahu <sudhan...@gmail.com> Sent: 27 December 2016 19:20:18 To: dev@cloudstack.apache.org Subject: Re: [DISCUSS][FUTURE] Move to JDK1.8 and s

Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Will Stevens
Haha. Rohit already did what I suggested. I am only just getting through my emails. :) On Dec 27, 2016 9:05 AM, "Will Stevens" wrote: > Maybe we should send an email to the dev and users lists with something > like this: > --- > Dropping F5 Support > The F5 plugin

Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Will Stevens
Maybe we should send an email to the dev and users lists with something like this: --- Dropping F5 Support The F5 plugin currently does not have any maintainers and it is holding us back from making an important move to Java 8. If you depend on this plugin, we recommend that you contact the dev@

Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Sudhansu Sahu
HI Rohit/ Wido, After adding below dependency to f5/pom.xml the build is successful. Below is the log for both FAILURE and successful BUILD. Sudhansus-MAC:f5 sudhansu$ java -version java version "1.8.0_65" Java(TM) SE Runtime Environment (build 1.8.0_65-b17) Java HotSpot(TM) 64-Bit Server VM

Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Wido den Hollander
> Op 27 december 2016 om 8:23 schreef Rohit Yadav : > > > All, > > > Java7 has eol-ed, it's about time to move to Java8 for both codebase and > runtime [1]. > > > An experimental PR [2] shows that moving to Java8 is fairly straight forward. > The only component

Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-27 Thread Erik Weber
I am +1 to removing code without maintainers, as long as it's not a core feature. Erik tir. 27. des. 2016 kl. 08.23 skrev Rohit Yadav : > All, > > > > > > Java7 has eol-ed, it's about time to move to Java8 for both codebase and > runtime [1]. > > > > > > An

RE: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-26 Thread Paul Angus
December 2016 07:24 To: dev@cloudstack.apache.org Subject: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8 All, Java7 has eol-ed, it's about time to move to Java8 for both codebase and runtime [1]. An experimental PR [2] shows that moving to Java8 is fairly straight forward. The only component

[DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8

2016-12-26 Thread Rohit Yadav
All, Java7 has eol-ed, it's about time to move to Java8 for both codebase and runtime [1]. An experimental PR [2] shows that moving to Java8 is fairly straight forward. The only component that is failing is F5 network plugin, which lacks authors/maintainers as this issue has been previously