is
jdk1.8 compatible.
[1]
https://github.com/rhtyd/cloudstack-nonoss/blob/master/install-non-oss.sh#L20
Regards.
From: Sudhansu Sahu
Sent: 27 December 2016 19:20:18
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS][FUTURE] Move to JDK1.8 and support JRE1.8
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 currently does not have any mai
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@ li
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 (bu
> 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 that is failing is F5 networ
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 experimental PR [2] shows that moving
I have no idea of the effort involved, so I'm going to pretend that it would be
easy.
It would be great if our plugin model for network functions could become more
of a driver model, such that these things could be developed and maintained
independantly of the ACS release cycles.
It would
