ect: Re: [Proposal] Switch to Java 7
>
> I would be in favor as well. In addition to the already discussed reasons, I
> think it would be good to try to get our users to a well maintained version of
> Java. From a security point of view 1.6 is not a smart choice any more.
>
> U
+1 for java 1.7
-Original Message-
From: Laszlo Hornyak [mailto:laszlo.horn...@gmail.com]
Sent: Wednesday, January 8, 2014 4:50 AM
To: dev@cloudstack.apache.org
Subject: Re: [Proposal] Switch to Java 7
+1 for java 1.7 and resource blocks, it will help to simplify
On Tue, Jan 7, 2014
+1 for java 1.7 and resource blocks, it will help to simplify
On Tue, Jan 7, 2014 at 11:50 PM, Hugo Trippaers wrote:
> I would be in favor as well. In addition to the already discussed reasons,
> I think it would be good to try to get our users to a well maintained
> version of Java. From a sec
I would be in favor as well. In addition to the already discussed reasons, I
think it would be good to try to get our users to a well maintained version of
Java. From a security point of view 1.6 is not a smart choice any more.
Upgrading to Jdk 7 could also trigger an upgrade to tomcat 7. Best p
+1 for switching to Java 7 in CloudStack 4.4.
Kelven
On 1/6/14, 10:27 PM, "Wido den Hollander" wrote:
>Just to repeat what has been discussed some time ago.
>
>All the current Long Term Support distributions have Java 7 available.
>
>RHEL6, RHEL7, Ubuntu 12.04, Ubuntu 14.04 (due in April) will
Just to repeat what has been discussed some time ago.
All the current Long Term Support distributions have Java 7 available.
RHEL6, RHEL7, Ubuntu 12.04, Ubuntu 14.04 (due in April) will all have
Java 7 available.
I don't see a problem in switching to Java 7 with CloudStack 4.4 or 4.5
Wido
O
Java 7 is preferred for Apache Hadoop but not required
http://wiki.apache.org/hadoop/HadoopJavaVersions
(I was looking to see if other OSS projects had migrated)
--
Chiradeep
> On Jan 6, 2014, at 6:16 PM, "Ryan Lei" wrote:
>
> There was yet another similar discussion a half-year ago:
> http://m
There was yet another similar discussion a half-year ago:
http://markmail.org/thread/ap6v46r3mdsgdszp
---
Yu-Heng (Ryan) Lei, Associate Researcher
Cloud Computing Dept, Chunghwa Telecom Labs
ryan...@cht.com.tw
Yes, it is for the same reason, to management resource leaking in a better
way. Java 7 finally has added this long-waited language feature. I’ve been
using JRE 7 with CloudStack for a while and didn’t see any alerted issues.
Kelven
On 1/6/14, 3:34 PM, "Chiradeep Vittal" wrote:
>Yes, there was a
Yes, there was another discussion here:
http://markmail.org/thread/uf6bxab6u4z4fmrp
On 1/6/14 3:18 PM, "Kelven Yang" wrote:
>Java 7 has been around for some time now. I strongly suggest CloudStack
>to adopt Java 7 as early as possible, the reason I feel like to raise the
>issue is from the som
Java 7 has been around for some time now. I strongly suggest CloudStack to
adopt Java 7 as early as possible, the reason I feel like to raise the issue is
from the some of practicing with the new DB transaction pattern, as following
example shows. The new Transaction pattern uses anonymous clas
11 matches
Mail list logo
