You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Wido den Hollander <wi...@widodh.nl> on 2013/02/25 12:23:39 UTC

[DISCUSS] Supported Java version

Hi,

So the last couple of days the master branch wouldn't build on my systems:

[INFO] Apache CloudStack Framework - IPC ................. FAILURE [1.874s]
...
...
[INFO] 
------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile 
(default-compile) on project cloud-framework-ipc: Compilation failure: 
Compilation failure:
[ERROR] 
/home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58] 
type parameters of <T>T cannot be determined; no unique maximal instance 
exists for type variable T with upper bounds T,java.lang.Object
[ERROR] 
/home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60] 
type parameters of <T>T cannot be determined; no unique maximal instance 
exists for type variable T with upper bounds T,java.lang.Object

So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop, 
servers) and this is the maven information:

wido@wido-desktop:~$ mvn -v
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family: "unix"
wido@wido-desktop:~$

Now, that Java version is old, I know, but it's the openjdk version 
which is in Ubuntu 12.04's repositories right now.

I downloaded Java 7:

wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn -v
Apache Maven 3.0.4
Maven home: /usr/share/maven
Java version: 1.7.0_15, vendor: Oracle Corporation
Java home: /opt/jdk1.7.0_15/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family: "unix"
wido@wido-desktop:~/repos/cloudstack$

With that Java version the master branch builds just fine.


What I want to discuss which version of Java we support.

I'd say we support the LTS version of any major release of CentOS or Ubuntu.

I also understand that Java 6 is pretty old, so what do we do?

Wido

Re: [DISCUSS] Supported Java version

Posted by Marcus Sorensen <sh...@gmail.com>.
Yes, this shouldn't be an issue for packaging/releases, because we can
just move the dependency to openjdk-7, CentOS/Ubuntu have both in
their standard repos.

On Mon, Feb 25, 2013 at 10:26 AM, John Burwell <jb...@basho.com> wrote:
> All,
>
> One clarification, I am speaking for 4.2, not 4.1.
>
> Thanks,
> -John
>
> On Feb 25, 2013, at 11:04 AM, John Burwell <jb...@basho.com> wrote:
>
>> Noa,
>>
>> I think of one very good reason -- as of this month, Java6 has been EOL'ed [1] by Oracle (i.e. no more updates).  Given the number of security issues that have cropped in Java lately, it seems prudent, in my mind, to ensure that the next release runs on an officially supported JRE.  Also, OpenJDK 7 is widely available for modern distributions (see openjdk-7 packages in Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
>>
>> Thanks,
>> -John
>>
>> [1]: http://www.oracle.com/technetwork/java/eol-135779.html
>> On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com> wrote:
>>
>>> Unless someone comes with a very good argument to drop java 6 compatibility
>>> (and make a good case for it in in public and gather consensus) I would
>>> consider this a bug that needs to be fixed.
>>>
>>> /noa
>>>
>>>
>>> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>wrote:
>>>
>>>> I didn't think that we agreed to bumping the java version to 7, and it
>>>> seems like that might make working with distros / packages difficult.
>>>>
>>>> Adding Alex and Frank to the CC to get their take.
>>>>
>>>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>>>> Hi,
>>>>>
>>>>> So the last couple of days the master branch wouldn't build on my
>>>> systems:
>>>>>
>>>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>>>> [1.874s]
>>>>> ...
>>>>> ...
>>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>>>> (default-compile) on project cloud-framework-ipc: Compilation
>>>>> failure: Compilation failure:
>>>>> [ERROR]
>>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>>> instance exists for type variable T with upper bounds
>>>>> T,java.lang.Object
>>>>> [ERROR]
>>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>>> instance exists for type variable T with upper bounds
>>>>> T,java.lang.Object
>>>>>
>>>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>>>> servers) and this is the maven information:
>>>>>
>>>>> wido@wido-desktop:~$ mvn -v
>>>>> Apache Maven 3.0.4
>>>>> Maven home: /usr/share/maven
>>>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>>> "unix"
>>>>> wido@wido-desktop:~$
>>>>>
>>>>> Now, that Java version is old, I know, but it's the openjdk version
>>>>> which is in Ubuntu 12.04's repositories right now.
>>>>>
>>>>> I downloaded Java 7:
>>>>>
>>>>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>>>> -v
>>>>> Apache Maven 3.0.4
>>>>> Maven home: /usr/share/maven
>>>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>>>> Java home: /opt/jdk1.7.0_15/jre
>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>>> "unix"
>>>>> wido@wido-desktop:~/repos/cloudstack$
>>>>>
>>>>> With that Java version the master branch builds just fine.
>>>>>
>>>>>
>>>>> What I want to discuss which version of Java we support.
>>>>>
>>>>> I'd say we support the LTS version of any major release of CentOS or
>>>> Ubuntu.
>>>>>
>>>>> I also understand that Java 6 is pretty old, so what do we do?
>>>>>
>>>>> Wido
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Engineering Experience, Infrastructure tribe, Spotify
>>
>

Re: [DISCUSS] Supported Java version

Posted by John Burwell <jb...@basho.com>.
All,

One clarification, I am speaking for 4.2, not 4.1.

Thanks,
-John

On Feb 25, 2013, at 11:04 AM, John Burwell <jb...@basho.com> wrote:

> Noa,
> 
> I think of one very good reason -- as of this month, Java6 has been EOL'ed [1] by Oracle (i.e. no more updates).  Given the number of security issues that have cropped in Java lately, it seems prudent, in my mind, to ensure that the next release runs on an officially supported JRE.  Also, OpenJDK 7 is widely available for modern distributions (see openjdk-7 packages in Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> 
> Thanks,
> -John
> 
> [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com> wrote:
> 
>> Unless someone comes with a very good argument to drop java 6 compatibility
>> (and make a good case for it in in public and gather consensus) I would
>> consider this a bug that needs to be fixed.
>> 
>> /noa
>> 
>> 
>> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>wrote:
>> 
>>> I didn't think that we agreed to bumping the java version to 7, and it
>>> seems like that might make working with distros / packages difficult.
>>> 
>>> Adding Alex and Frank to the CC to get their take.
>>> 
>>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>>> Hi,
>>>> 
>>>> So the last couple of days the master branch wouldn't build on my
>>> systems:
>>>> 
>>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>>> [1.874s]
>>>> ...
>>>> ...
>>>> [INFO]
>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>>> (default-compile) on project cloud-framework-ipc: Compilation
>>>> failure: Compilation failure:
>>>> [ERROR]
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object
>>>> [ERROR]
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object
>>>> 
>>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>>> servers) and this is the maven information:
>>>> 
>>>> wido@wido-desktop:~$ mvn -v
>>>> Apache Maven 3.0.4
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>> "unix"
>>>> wido@wido-desktop:~$
>>>> 
>>>> Now, that Java version is old, I know, but it's the openjdk version
>>>> which is in Ubuntu 12.04's repositories right now.
>>>> 
>>>> I downloaded Java 7:
>>>> 
>>>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>>> -v
>>>> Apache Maven 3.0.4
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>>> Java home: /opt/jdk1.7.0_15/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>> "unix"
>>>> wido@wido-desktop:~/repos/cloudstack$
>>>> 
>>>> With that Java version the master branch builds just fine.
>>>> 
>>>> 
>>>> What I want to discuss which version of Java we support.
>>>> 
>>>> I'd say we support the LTS version of any major release of CentOS or
>>> Ubuntu.
>>>> 
>>>> I also understand that Java 6 is pretty old, so what do we do?
>>>> 
>>>> Wido
>>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> Engineering Experience, Infrastructure tribe, Spotify
> 


RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
Sudha,

I created https://issues.apache.org/jira/browse/CLOUDSTACK-1421 and assigned it to Kelven.

I don't believe we will have any difficulty running against the 1.7 JRE.  Just need a quick test to make sure.

--Alex

> -----Original Message-----
> From: Sudha Ponnaganti
> Sent: Tuesday, February 26, 2013 2:14 PM
> To: cloudstack-dev@incubator.apache.org; Alex Huang
> Cc: Noa Resare; Frank Zhang; Kelven Yang
> Subject: RE: [DISCUSS] Supported Java version
> 
> However, can you confirm that none of the features depend on JRE and the
> impact is low if we use 1.7.
> 
> 
> -----Original Message-----
> From: Sudha Ponnaganti [mailto:sudha.ponnaganti@citrix.com]
> Sent: Tuesday, February 26, 2013 2:09 PM
> To: Alex Huang; cloudstack-dev@incubator.apache.org
> Cc: Noa Resare; Frank Zhang; Kelven Yang
> Subject: RE: [DISCUSS] Supported Java version
> 
> I have been reviewing this mail thread to see the impact.  So far we haven't
> used 1.7 but if this is confirmed then we will include it in the matrix to be
> covered
> 
> -----Original Message-----
> From: Alex Huang
> Sent: Tuesday, February 26, 2013 1:51 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Noa Resare; Frank Zhang; Sudha Ponnaganti; Kelven Yang
> Subject: RE: [DISCUSS] Supported Java version
> 
> John,
> 
> I hate to see us disagree if even our agreements are violent!  :) (he he...I
> know what violent agreement means but just couldn't resist.)
> 
> The reason I brought this up is that Wido said in the original message that 4.1
> now no longer compiles under 1.6 and must use 1.7 to compile.  That we've
> gotta fix.
> 
> I cced Sudha so she can plan to test with JRE 7.
> I cced Kelven because it's his IPC code that causes this problem with 1.6.
> 
> I've gotta say that I've been running with 1.7 and so far no problems.  So I
> don't really expect problems.
> 
> --Alex
> 
> > -----Original Message-----
> > From: John Burwell [mailto:jburwell@basho.com]
> > Sent: Tuesday, February 26, 2013 1:43 PM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Noa Resare; Frank Zhang
> > Subject: Re: [DISCUSS] Supported Java version
> >
> > Alex,
> >
> > I think we are in violent agreement.  I am only advocating for a build
> > tested on JRE7, and listed as officially supported in our docs.  Using
> > the Java7 features is a completely different discussion.
> >
> > Thanks,
> > -John
> >
> > On Feb 26, 2013, at 3:52 PM, Alex Huang <al...@citrix.com> wrote:
> >
> > > +1 That's exactly what I said in my reply as well.  Support for
> > > +Java7 means
> > we test with JRE7 in 4.1 but support for Java7 does not mean we should
> > push for deprecating JRE6 support.
> > >
> > > --Alex
> > >
> > > From: Noa Resare [mailto:noa@spotify.com]
> > > Sent: Tuesday, February 26, 2013 12:35 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Cc: Frank Zhang; Alex Huang
> > > Subject: Re: [DISCUSS] Supported Java version
> > >
> > > java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping
> > > as part
> > of the enterprise distributions and as such will be supported in i.e.
> > Debian Wheezy for at least years into the future.
> > >
> > > I'm not talking about not supporting java 7, the java ecosystem has
> > traditionally been very good at supporting code targeting
> > current_version - 1, but I propose we avoid using language features
> > and quirks that break java 6 compatibility.
> > >
> > > /n
> > >
> > > On Mon, Feb 25, 2013 at 5:04 PM, John Burwell
> > <jb...@basho.com>> wrote:
> > > Noa,
> > >
> > > I think of one very good reason -- as of this month, Java6 has been
> > > EOL'ed
> > [1] by Oracle (i.e. no more updates).  Given the number of security
> > issues that have cropped in Java lately, it seems prudent, in my mind,
> > to ensure that the next release runs on an officially supported JRE.
> > Also, OpenJDK 7 is widely available for modern distributions (see
> > openjdk-7 packages in Ubuntu
> > 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> > >
> > > Thanks,
> > > -John
> > >
> > > [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> > > On Feb 25, 2013, at 10:24 AM, Noa Resare
> > <no...@spotify.com>> wrote:
> > >
> > >> Unless someone comes with a very good argument to drop java 6
> > >> compatibility (and make a good case for it in in public and gather
> > >> consensus) I would consider this a bug that needs to be fixed.
> > >>
> > >> /noa
> > >>
> > >>
> > >> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers
> > <ch...@sungard.com>>wrote:
> > >>
> > >>> I didn't think that we agreed to bumping the java version to 7,
> > >>> and it seems like that might make working with distros / packages
> difficult.
> > >>>
> > >>> Adding Alex and Frank to the CC to get their take.
> > >>>
> > >>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> > >>>> Hi,
> > >>>>
> > >>>> So the last couple of days the master branch wouldn't build on my
> > >>> systems:
> > >>>>
> > >>>> [INFO] Apache CloudStack Framework - IPC .................
> > >>>> FAILURE
> > >>> [1.874s]
> > >>>> ...
> > >>>> ...
> > >>>> [INFO]
> > >>> ------------------------------------------------------------------
> > >>> --
> > >>> ----
> > >>>> [ERROR] Failed to execute goal
> > >>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> > >>>> (default-compile) on project cloud-framework-ipc: Compilation
> > >>>> failure: Compilation failure:
> > >>>> [ERROR]
> > >>>
> >
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> > >>> oudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> > >>>> type parameters of <T>T cannot be determined; no unique maximal
> > >>>> instance exists for type variable T with upper bounds
> > >>>> T,java.lang.Object [ERROR]
> > >>>
> >
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> > >>> oudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> > >>>> type parameters of <T>T cannot be determined; no unique maximal
> > >>>> instance exists for type variable T with upper bounds
> > >>>> T,java.lang.Object
> > >>>>
> > >>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> > >>>> servers) and this is the maven information:
> > >>>>
> > >>>> wido@wido-desktop:~$ mvn -v
> > >>>> Apache Maven 3.0.4
> > >>>> Maven home: /usr/share/maven
> > >>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> > >>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> > >>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> > >>>> version: "3.2.0-38-generic", arch: "amd64", family:
> > >>> "unix"
> > >>>> wido@wido-desktop:~$
> > >>>>
> > >>>> Now, that Java version is old, I know, but it's the openjdk
> > >>>> version which is in Ubuntu 12.04's repositories right now.
> > >>>>
> > >>>> I downloaded Java 7:
> > >>>>
> > >>>> wido@wido-
> > desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15"
> > >>>> mvn
> > >>> -v
> > >>>> Apache Maven 3.0.4
> > >>>> Maven home: /usr/share/maven
> > >>>> Java version: 1.7.0_15, vendor: Oracle Corporation Java home:
> > >>>> /opt/jdk1.7.0_15/jre Default locale: en_US, platform encoding:
> > >>>> UTF-8 OS name: "linux", version: "3.2.0-38-generic", arch:
> > >>>> "amd64",
> > >>>> family:
> > >>> "unix"
> > >>>> wido@wido-desktop:~/repos/cloudstack$
> > >>>>
> > >>>> With that Java version the master branch builds just fine.
> > >>>>
> > >>>>
> > >>>> What I want to discuss which version of Java we support.
> > >>>>
> > >>>> I'd say we support the LTS version of any major release of CentOS
> > >>>> or
> > >>> Ubuntu.
> > >>>>
> > >>>> I also understand that Java 6 is pretty old, so what do we do?
> > >>>>
> > >>>> Wido
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Engineering Experience, Infrastructure tribe, Spotify
> > >
> > >
> > >
> > > --
> > > Engineering Experience, Infrastructure tribe, Spotify
> > >


RE: [DISCUSS] Supported Java version

Posted by Sudha Ponnaganti <su...@citrix.com>.
However, can you confirm that none of the features depend on JRE and the impact is low if we use 1.7.


-----Original Message-----
From: Sudha Ponnaganti [mailto:sudha.ponnaganti@citrix.com] 
Sent: Tuesday, February 26, 2013 2:09 PM
To: Alex Huang; cloudstack-dev@incubator.apache.org
Cc: Noa Resare; Frank Zhang; Kelven Yang
Subject: RE: [DISCUSS] Supported Java version

I have been reviewing this mail thread to see the impact.  So far we haven't used 1.7 but if this is confirmed then we will include it in the matrix to be covered

-----Original Message-----
From: Alex Huang
Sent: Tuesday, February 26, 2013 1:51 PM
To: cloudstack-dev@incubator.apache.org
Cc: Noa Resare; Frank Zhang; Sudha Ponnaganti; Kelven Yang
Subject: RE: [DISCUSS] Supported Java version

John,

I hate to see us disagree if even our agreements are violent!  :) (he he...I know what violent agreement means but just couldn't resist.)

The reason I brought this up is that Wido said in the original message that 4.1 now no longer compiles under 1.6 and must use 1.7 to compile.  That we've gotta fix.  

I cced Sudha so she can plan to test with JRE 7.
I cced Kelven because it's his IPC code that causes this problem with 1.6.

I've gotta say that I've been running with 1.7 and so far no problems.  So I don't really expect problems.

--Alex

> -----Original Message-----
> From: John Burwell [mailto:jburwell@basho.com]
> Sent: Tuesday, February 26, 2013 1:43 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Noa Resare; Frank Zhang
> Subject: Re: [DISCUSS] Supported Java version
> 
> Alex,
> 
> I think we are in violent agreement.  I am only advocating for a build 
> tested on JRE7, and listed as officially supported in our docs.  Using 
> the Java7 features is a completely different discussion.
> 
> Thanks,
> -John
> 
> On Feb 26, 2013, at 3:52 PM, Alex Huang <al...@citrix.com> wrote:
> 
> > +1 That's exactly what I said in my reply as well.  Support for
> > +Java7 means
> we test with JRE7 in 4.1 but support for Java7 does not mean we should 
> push for deprecating JRE6 support.
> >
> > --Alex
> >
> > From: Noa Resare [mailto:noa@spotify.com]
> > Sent: Tuesday, February 26, 2013 12:35 PM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Frank Zhang; Alex Huang
> > Subject: Re: [DISCUSS] Supported Java version
> >
> > java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping 
> > as part
> of the enterprise distributions and as such will be supported in i.e. 
> Debian Wheezy for at least years into the future.
> >
> > I'm not talking about not supporting java 7, the java ecosystem has
> traditionally been very good at supporting code targeting 
> current_version - 1, but I propose we avoid using language features 
> and quirks that break java 6 compatibility.
> >
> > /n
> >
> > On Mon, Feb 25, 2013 at 5:04 PM, John Burwell
> <jb...@basho.com>> wrote:
> > Noa,
> >
> > I think of one very good reason -- as of this month, Java6 has been 
> > EOL'ed
> [1] by Oracle (i.e. no more updates).  Given the number of security 
> issues that have cropped in Java lately, it seems prudent, in my mind, 
> to ensure that the next release runs on an officially supported JRE.
> Also, OpenJDK 7 is widely available for modern distributions (see
> openjdk-7 packages in Ubuntu
> 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> >
> > Thanks,
> > -John
> >
> > [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> > On Feb 25, 2013, at 10:24 AM, Noa Resare
> <no...@spotify.com>> wrote:
> >
> >> Unless someone comes with a very good argument to drop java 6 
> >> compatibility (and make a good case for it in in public and gather
> >> consensus) I would consider this a bug that needs to be fixed.
> >>
> >> /noa
> >>
> >>
> >> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers
> <ch...@sungard.com>>wrote:
> >>
> >>> I didn't think that we agreed to bumping the java version to 7, 
> >>> and it seems like that might make working with distros / packages difficult.
> >>>
> >>> Adding Alex and Frank to the CC to get their take.
> >>>
> >>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> >>>> Hi,
> >>>>
> >>>> So the last couple of days the master branch wouldn't build on my
> >>> systems:
> >>>>
> >>>> [INFO] Apache CloudStack Framework - IPC ................. 
> >>>> FAILURE
> >>> [1.874s]
> >>>> ...
> >>>> ...
> >>>> [INFO]
> >>> ------------------------------------------------------------------
> >>> --
> >>> ----
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> >>>> (default-compile) on project cloud-framework-ipc: Compilation
> >>>> failure: Compilation failure:
> >>>> [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> >>>> type parameters of <T>T cannot be determined; no unique maximal 
> >>>> instance exists for type variable T with upper bounds 
> >>>> T,java.lang.Object [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> >>>> type parameters of <T>T cannot be determined; no unique maximal 
> >>>> instance exists for type variable T with upper bounds 
> >>>> T,java.lang.Object
> >>>>
> >>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> >>>> servers) and this is the maven information:
> >>>>
> >>>> wido@wido-desktop:~$ mvn -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> >>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> >>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> >>>> version: "3.2.0-38-generic", arch: "amd64", family:
> >>> "unix"
> >>>> wido@wido-desktop:~$
> >>>>
> >>>> Now, that Java version is old, I know, but it's the openjdk 
> >>>> version which is in Ubuntu 12.04's repositories right now.
> >>>>
> >>>> I downloaded Java 7:
> >>>>
> >>>> wido@wido-
> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15"
> >>>> mvn
> >>> -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.7.0_15, vendor: Oracle Corporation Java home:
> >>>> /opt/jdk1.7.0_15/jre Default locale: en_US, platform encoding:
> >>>> UTF-8 OS name: "linux", version: "3.2.0-38-generic", arch: 
> >>>> "amd64",
> >>>> family:
> >>> "unix"
> >>>> wido@wido-desktop:~/repos/cloudstack$
> >>>>
> >>>> With that Java version the master branch builds just fine.
> >>>>
> >>>>
> >>>> What I want to discuss which version of Java we support.
> >>>>
> >>>> I'd say we support the LTS version of any major release of CentOS 
> >>>> or
> >>> Ubuntu.
> >>>>
> >>>> I also understand that Java 6 is pretty old, so what do we do?
> >>>>
> >>>> Wido
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Engineering Experience, Infrastructure tribe, Spotify
> >
> >
> >
> > --
> > Engineering Experience, Infrastructure tribe, Spotify
> >


RE: [DISCUSS] Supported Java version

Posted by Sudha Ponnaganti <su...@citrix.com>.
I have been reviewing this mail thread to see the impact.  So far we haven't used 1.7 but if this is confirmed then we will include it in the matrix to be covered

-----Original Message-----
From: Alex Huang 
Sent: Tuesday, February 26, 2013 1:51 PM
To: cloudstack-dev@incubator.apache.org
Cc: Noa Resare; Frank Zhang; Sudha Ponnaganti; Kelven Yang
Subject: RE: [DISCUSS] Supported Java version

John,

I hate to see us disagree if even our agreements are violent!  :) (he he...I know what violent agreement means but just couldn't resist.)

The reason I brought this up is that Wido said in the original message that 4.1 now no longer compiles under 1.6 and must use 1.7 to compile.  That we've gotta fix.  

I cced Sudha so she can plan to test with JRE 7.
I cced Kelven because it's his IPC code that causes this problem with 1.6.

I've gotta say that I've been running with 1.7 and so far no problems.  So I don't really expect problems.

--Alex

> -----Original Message-----
> From: John Burwell [mailto:jburwell@basho.com]
> Sent: Tuesday, February 26, 2013 1:43 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Noa Resare; Frank Zhang
> Subject: Re: [DISCUSS] Supported Java version
> 
> Alex,
> 
> I think we are in violent agreement.  I am only advocating for a build 
> tested on JRE7, and listed as officially supported in our docs.  Using 
> the Java7 features is a completely different discussion.
> 
> Thanks,
> -John
> 
> On Feb 26, 2013, at 3:52 PM, Alex Huang <al...@citrix.com> wrote:
> 
> > +1 That's exactly what I said in my reply as well.  Support for 
> > +Java7 means
> we test with JRE7 in 4.1 but support for Java7 does not mean we should 
> push for deprecating JRE6 support.
> >
> > --Alex
> >
> > From: Noa Resare [mailto:noa@spotify.com]
> > Sent: Tuesday, February 26, 2013 12:35 PM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Frank Zhang; Alex Huang
> > Subject: Re: [DISCUSS] Supported Java version
> >
> > java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping 
> > as part
> of the enterprise distributions and as such will be supported in i.e. 
> Debian Wheezy for at least years into the future.
> >
> > I'm not talking about not supporting java 7, the java ecosystem has
> traditionally been very good at supporting code targeting 
> current_version - 1, but I propose we avoid using language features 
> and quirks that break java 6 compatibility.
> >
> > /n
> >
> > On Mon, Feb 25, 2013 at 5:04 PM, John Burwell
> <jb...@basho.com>> wrote:
> > Noa,
> >
> > I think of one very good reason -- as of this month, Java6 has been 
> > EOL'ed
> [1] by Oracle (i.e. no more updates).  Given the number of security 
> issues that have cropped in Java lately, it seems prudent, in my mind, 
> to ensure that the next release runs on an officially supported JRE.  
> Also, OpenJDK 7 is widely available for modern distributions (see 
> openjdk-7 packages in Ubuntu
> 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> >
> > Thanks,
> > -John
> >
> > [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> > On Feb 25, 2013, at 10:24 AM, Noa Resare
> <no...@spotify.com>> wrote:
> >
> >> Unless someone comes with a very good argument to drop java 6 
> >> compatibility (and make a good case for it in in public and gather
> >> consensus) I would consider this a bug that needs to be fixed.
> >>
> >> /noa
> >>
> >>
> >> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers
> <ch...@sungard.com>>wrote:
> >>
> >>> I didn't think that we agreed to bumping the java version to 7, 
> >>> and it seems like that might make working with distros / packages difficult.
> >>>
> >>> Adding Alex and Frank to the CC to get their take.
> >>>
> >>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> >>>> Hi,
> >>>>
> >>>> So the last couple of days the master branch wouldn't build on my
> >>> systems:
> >>>>
> >>>> [INFO] Apache CloudStack Framework - IPC ................. 
> >>>> FAILURE
> >>> [1.874s]
> >>>> ...
> >>>> ...
> >>>> [INFO]
> >>> ------------------------------------------------------------------
> >>> --
> >>> ----
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> >>>> (default-compile) on project cloud-framework-ipc: Compilation
> >>>> failure: Compilation failure:
> >>>> [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> >>>> type parameters of <T>T cannot be determined; no unique maximal 
> >>>> instance exists for type variable T with upper bounds 
> >>>> T,java.lang.Object [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> >>>> type parameters of <T>T cannot be determined; no unique maximal 
> >>>> instance exists for type variable T with upper bounds 
> >>>> T,java.lang.Object
> >>>>
> >>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> >>>> servers) and this is the maven information:
> >>>>
> >>>> wido@wido-desktop:~$ mvn -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> >>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> >>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> >>>> version: "3.2.0-38-generic", arch: "amd64", family:
> >>> "unix"
> >>>> wido@wido-desktop:~$
> >>>>
> >>>> Now, that Java version is old, I know, but it's the openjdk 
> >>>> version which is in Ubuntu 12.04's repositories right now.
> >>>>
> >>>> I downloaded Java 7:
> >>>>
> >>>> wido@wido-
> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15"
> >>>> mvn
> >>> -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.7.0_15, vendor: Oracle Corporation Java home:
> >>>> /opt/jdk1.7.0_15/jre Default locale: en_US, platform encoding:
> >>>> UTF-8 OS name: "linux", version: "3.2.0-38-generic", arch: 
> >>>> "amd64",
> >>>> family:
> >>> "unix"
> >>>> wido@wido-desktop:~/repos/cloudstack$
> >>>>
> >>>> With that Java version the master branch builds just fine.
> >>>>
> >>>>
> >>>> What I want to discuss which version of Java we support.
> >>>>
> >>>> I'd say we support the LTS version of any major release of CentOS 
> >>>> or
> >>> Ubuntu.
> >>>>
> >>>> I also understand that Java 6 is pretty old, so what do we do?
> >>>>
> >>>> Wido
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Engineering Experience, Infrastructure tribe, Spotify
> >
> >
> >
> > --
> > Engineering Experience, Infrastructure tribe, Spotify
> >


RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
John,

I hate to see us disagree if even our agreements are violent!  :) (he he...I know what violent agreement means but just couldn't resist.)

The reason I brought this up is that Wido said in the original message that 4.1 now no longer compiles under 1.6 and must use 1.7 to compile.  That we've gotta fix.  

I cced Sudha so she can plan to test with JRE 7.
I cced Kelven because it's his IPC code that causes this problem with 1.6.

I've gotta say that I've been running with 1.7 and so far no problems.  So I don't really expect problems.

--Alex

> -----Original Message-----
> From: John Burwell [mailto:jburwell@basho.com]
> Sent: Tuesday, February 26, 2013 1:43 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Noa Resare; Frank Zhang
> Subject: Re: [DISCUSS] Supported Java version
> 
> Alex,
> 
> I think we are in violent agreement.  I am only advocating for a build tested
> on JRE7, and listed as officially supported in our docs.  Using the Java7
> features is a completely different discussion.
> 
> Thanks,
> -John
> 
> On Feb 26, 2013, at 3:52 PM, Alex Huang <al...@citrix.com> wrote:
> 
> > +1 That's exactly what I said in my reply as well.  Support for Java7 means
> we test with JRE7 in 4.1 but support for Java7 does not mean we should push
> for deprecating JRE6 support.
> >
> > --Alex
> >
> > From: Noa Resare [mailto:noa@spotify.com]
> > Sent: Tuesday, February 26, 2013 12:35 PM
> > To: cloudstack-dev@incubator.apache.org
> > Cc: Frank Zhang; Alex Huang
> > Subject: Re: [DISCUSS] Supported Java version
> >
> > java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as part
> of the enterprise distributions and as such will be supported in i.e. Debian
> Wheezy for at least years into the future.
> >
> > I'm not talking about not supporting java 7, the java ecosystem has
> traditionally been very good at supporting code targeting current_version - 1,
> but I propose we avoid using language features and quirks that break java 6
> compatibility.
> >
> > /n
> >
> > On Mon, Feb 25, 2013 at 5:04 PM, John Burwell
> <jb...@basho.com>> wrote:
> > Noa,
> >
> > I think of one very good reason -- as of this month, Java6 has been EOL'ed
> [1] by Oracle (i.e. no more updates).  Given the number of security issues
> that have cropped in Java lately, it seems prudent, in my mind, to ensure that
> the next release runs on an officially supported JRE.  Also, OpenJDK 7 is
> widely available for modern distributions (see openjdk-7 packages in Ubuntu
> 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> >
> > Thanks,
> > -John
> >
> > [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> > On Feb 25, 2013, at 10:24 AM, Noa Resare
> <no...@spotify.com>> wrote:
> >
> >> Unless someone comes with a very good argument to drop java 6
> >> compatibility (and make a good case for it in in public and gather
> >> consensus) I would consider this a bug that needs to be fixed.
> >>
> >> /noa
> >>
> >>
> >> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers
> <ch...@sungard.com>>wrote:
> >>
> >>> I didn't think that we agreed to bumping the java version to 7, and
> >>> it seems like that might make working with distros / packages difficult.
> >>>
> >>> Adding Alex and Frank to the CC to get their take.
> >>>
> >>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> >>>> Hi,
> >>>>
> >>>> So the last couple of days the master branch wouldn't build on my
> >>> systems:
> >>>>
> >>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
> >>> [1.874s]
> >>>> ...
> >>>> ...
> >>>> [INFO]
> >>> --------------------------------------------------------------------
> >>> ----
> >>>> [ERROR] Failed to execute goal
> >>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> >>>> (default-compile) on project cloud-framework-ipc: Compilation
> >>>> failure: Compilation failure:
> >>>> [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> >>>> type parameters of <T>T cannot be determined; no unique maximal
> >>>> instance exists for type variable T with upper bounds
> >>>> T,java.lang.Object [ERROR]
> >>>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> >>> oudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> >>>> type parameters of <T>T cannot be determined; no unique maximal
> >>>> instance exists for type variable T with upper bounds
> >>>> T,java.lang.Object
> >>>>
> >>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> >>>> servers) and this is the maven information:
> >>>>
> >>>> wido@wido-desktop:~$ mvn -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> >>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> >>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> >>>> version: "3.2.0-38-generic", arch: "amd64", family:
> >>> "unix"
> >>>> wido@wido-desktop:~$
> >>>>
> >>>> Now, that Java version is old, I know, but it's the openjdk version
> >>>> which is in Ubuntu 12.04's repositories right now.
> >>>>
> >>>> I downloaded Java 7:
> >>>>
> >>>> wido@wido-
> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15"
> >>>> mvn
> >>> -v
> >>>> Apache Maven 3.0.4
> >>>> Maven home: /usr/share/maven
> >>>> Java version: 1.7.0_15, vendor: Oracle Corporation Java home:
> >>>> /opt/jdk1.7.0_15/jre Default locale: en_US, platform encoding:
> >>>> UTF-8 OS name: "linux", version: "3.2.0-38-generic", arch: "amd64",
> >>>> family:
> >>> "unix"
> >>>> wido@wido-desktop:~/repos/cloudstack$
> >>>>
> >>>> With that Java version the master branch builds just fine.
> >>>>
> >>>>
> >>>> What I want to discuss which version of Java we support.
> >>>>
> >>>> I'd say we support the LTS version of any major release of CentOS
> >>>> or
> >>> Ubuntu.
> >>>>
> >>>> I also understand that Java 6 is pretty old, so what do we do?
> >>>>
> >>>> Wido
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Engineering Experience, Infrastructure tribe, Spotify
> >
> >
> >
> > --
> > Engineering Experience, Infrastructure tribe, Spotify
> >


Re: [DISCUSS] Supported Java version

Posted by John Burwell <jb...@basho.com>.
Alex,

I think we are in violent agreement.  I am only advocating for a build tested on JRE7, and listed as officially supported in our docs.  Using the Java7 features is a completely different discussion.

Thanks,
-John

On Feb 26, 2013, at 3:52 PM, Alex Huang <al...@citrix.com> wrote:

> +1 That's exactly what I said in my reply as well.  Support for Java7 means we test with JRE7 in 4.1 but support for Java7 does not mean we should push for deprecating JRE6 support.
> 
> --Alex
> 
> From: Noa Resare [mailto:noa@spotify.com]
> Sent: Tuesday, February 26, 2013 12:35 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Frank Zhang; Alex Huang
> Subject: Re: [DISCUSS] Supported Java version
> 
> java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as part of the enterprise distributions and as such will be supported in i.e. Debian Wheezy for at least years into the future.
> 
> I'm not talking about not supporting java 7, the java ecosystem has traditionally been very good at supporting code targeting current_version - 1, but I propose we avoid using language features and quirks that break java 6 compatibility.
> 
> /n
> 
> On Mon, Feb 25, 2013 at 5:04 PM, John Burwell <jb...@basho.com>> wrote:
> Noa,
> 
> I think of one very good reason -- as of this month, Java6 has been EOL'ed [1] by Oracle (i.e. no more updates).  Given the number of security issues that have cropped in Java lately, it seems prudent, in my mind, to ensure that the next release runs on an officially supported JRE.  Also, OpenJDK 7 is widely available for modern distributions (see openjdk-7 packages in Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
> 
> Thanks,
> -John
> 
> [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com>> wrote:
> 
>> Unless someone comes with a very good argument to drop java 6 compatibility
>> (and make a good case for it in in public and gather consensus) I would
>> consider this a bug that needs to be fixed.
>> 
>> /noa
>> 
>> 
>> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>>wrote:
>> 
>>> I didn't think that we agreed to bumping the java version to 7, and it
>>> seems like that might make working with distros / packages difficult.
>>> 
>>> Adding Alex and Frank to the CC to get their take.
>>> 
>>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>>> Hi,
>>>> 
>>>> So the last couple of days the master branch wouldn't build on my
>>> systems:
>>>> 
>>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>>> [1.874s]
>>>> ...
>>>> ...
>>>> [INFO]
>>> ------------------------------------------------------------------------
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>>> (default-compile) on project cloud-framework-ipc: Compilation
>>>> failure: Compilation failure:
>>>> [ERROR]
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object
>>>> [ERROR]
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object
>>>> 
>>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>>> servers) and this is the maven information:
>>>> 
>>>> wido@wido-desktop:~$ mvn -v
>>>> Apache Maven 3.0.4
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>> "unix"
>>>> wido@wido-desktop:~$
>>>> 
>>>> Now, that Java version is old, I know, but it's the openjdk version
>>>> which is in Ubuntu 12.04's repositories right now.
>>>> 
>>>> I downloaded Java 7:
>>>> 
>>>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>>> -v
>>>> Apache Maven 3.0.4
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>>> Java home: /opt/jdk1.7.0_15/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>>> "unix"
>>>> wido@wido-desktop:~/repos/cloudstack$
>>>> 
>>>> With that Java version the master branch builds just fine.
>>>> 
>>>> 
>>>> What I want to discuss which version of Java we support.
>>>> 
>>>> I'd say we support the LTS version of any major release of CentOS or
>>> Ubuntu.
>>>> 
>>>> I also understand that Java 6 is pretty old, so what do we do?
>>>> 
>>>> Wido
>>>> 
>>> 
>> 
>> 
>> 
>> --
>> Engineering Experience, Infrastructure tribe, Spotify
> 
> 
> 
> --
> Engineering Experience, Infrastructure tribe, Spotify
> 


RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
+1 That's exactly what I said in my reply as well.  Support for Java7 means we test with JRE7 in 4.1 but support for Java7 does not mean we should push for deprecating JRE6 support.

--Alex

From: Noa Resare [mailto:noa@spotify.com]
Sent: Tuesday, February 26, 2013 12:35 PM
To: cloudstack-dev@incubator.apache.org
Cc: Frank Zhang; Alex Huang
Subject: Re: [DISCUSS] Supported Java version

java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as part of the enterprise distributions and as such will be supported in i.e. Debian Wheezy for at least years into the future.

I'm not talking about not supporting java 7, the java ecosystem has traditionally been very good at supporting code targeting current_version - 1, but I propose we avoid using language features and quirks that break java 6 compatibility.

/n

On Mon, Feb 25, 2013 at 5:04 PM, John Burwell <jb...@basho.com>> wrote:
Noa,

I think of one very good reason -- as of this month, Java6 has been EOL'ed [1] by Oracle (i.e. no more updates).  Given the number of security issues that have cropped in Java lately, it seems prudent, in my mind, to ensure that the next release runs on an officially supported JRE.  Also, OpenJDK 7 is widely available for modern distributions (see openjdk-7 packages in Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).

Thanks,
-John

[1]: http://www.oracle.com/technetwork/java/eol-135779.html
On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com>> wrote:

> Unless someone comes with a very good argument to drop java 6 compatibility
> (and make a good case for it in in public and gather consensus) I would
> consider this a bug that needs to be fixed.
>
> /noa
>
>
> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>>wrote:
>
>> I didn't think that we agreed to bumping the java version to 7, and it
>> seems like that might make working with distros / packages difficult.
>>
>> Adding Alex and Frank to the CC to get their take.
>>
>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>> Hi,
>>>
>>> So the last couple of days the master branch wouldn't build on my
>> systems:
>>>
>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>> [1.874s]
>>> ...
>>> ...
>>> [INFO]
>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>> (default-compile) on project cloud-framework-ipc: Compilation
>>> failure: Compilation failure:
>>> [ERROR]
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object
>>> [ERROR]
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object
>>>
>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>> servers) and this is the maven information:
>>>
>>> wido@wido-desktop:~$ mvn -v
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>> "unix"
>>> wido@wido-desktop:~$
>>>
>>> Now, that Java version is old, I know, but it's the openjdk version
>>> which is in Ubuntu 12.04's repositories right now.
>>>
>>> I downloaded Java 7:
>>>
>>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>> -v
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>> Java home: /opt/jdk1.7.0_15/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>> "unix"
>>> wido@wido-desktop:~/repos/cloudstack$
>>>
>>> With that Java version the master branch builds just fine.
>>>
>>>
>>> What I want to discuss which version of Java we support.
>>>
>>> I'd say we support the LTS version of any major release of CentOS or
>> Ubuntu.
>>>
>>> I also understand that Java 6 is pretty old, so what do we do?
>>>
>>> Wido
>>>
>>
>
>
>
> --
> Engineering Experience, Infrastructure tribe, Spotify



--
Engineering Experience, Infrastructure tribe, Spotify


RE: [DISCUSS] Supported Java version

Posted by Frank Zhang <Fr...@citrix.com>.
A curious question.
Do we see any Java feature that may block compatibility between 1.6 and 1.7?
IMO, CloudStack uses common java features that should work well on JRE greater than 1.5

> -----Original Message-----
> From: Joe Brockmeier [mailto:jzb@zonker.net]
> Sent: Wednesday, February 27, 2013 9:00 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Supported Java version
> 
> On Tue, Feb 26, 2013, at 02:34 PM, Noa Resare wrote:
> > java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as
> > part of the enterprise distributions and as such will be supported in
> > i.e.
> > Debian Wheezy for at least years into the future.
> 
> If the upstream project is no longer supporting OpenJDK 6, I'm wondering
> about the time it will take to address any new security issues, etc.
> 
> Just digging into this a little, I see this:
> 
> http://packages.qa.debian.org/o/openjdk-6.html
> 
> Top todo item:
> 
> "There are 122 open security issues, please fix them."
> 
> (OpenJDK 7 shows 16 open issues.)
> 
> > I'm not talking about not supporting java 7, the java ecosystem has
> > traditionally been very good at supporting code targeting
> > current_version
> > -
> > 1, but I propose we avoid using language features and quirks that
> > break java 6 compatibility.
> 
> That seems reasonable, assuming there's nothing in Java 7 we need/want.
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Re: [DISCUSS] Supported Java version

Posted by Joe Brockmeier <jz...@zonker.net>.
On Tue, Feb 26, 2013, at 02:34 PM, Noa Resare wrote:
> java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as
> part
> of the enterprise distributions and as such will be supported in i.e.
> Debian Wheezy for at least years into the future.

If the upstream project is no longer supporting OpenJDK 6, I'm wondering
about the time it will take to address any new security issues, etc. 

Just digging into this a little, I see this:

http://packages.qa.debian.org/o/openjdk-6.html

Top todo item:

"There are 122 open security issues, please fix them."

(OpenJDK 7 shows 16 open issues.) 
 
> I'm not talking about not supporting java 7, the java ecosystem has
> traditionally been very good at supporting code targeting current_version
> -
> 1, but I propose we avoid using language features and quirks that break
> java 6 compatibility.

That seems reasonable, assuming there's nothing in Java 7 we need/want.

Best,

jzb
-- 
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: [DISCUSS] Supported Java version

Posted by Noa Resare <no...@spotify.com>.
java 6 may be end-of-line'd by Oracle, but the OpenJDK is shipping as part
of the enterprise distributions and as such will be supported in i.e.
Debian Wheezy for at least years into the future.

I'm not talking about not supporting java 7, the java ecosystem has
traditionally been very good at supporting code targeting current_version -
1, but I propose we avoid using language features and quirks that break
java 6 compatibility.

/n


On Mon, Feb 25, 2013 at 5:04 PM, John Burwell <jb...@basho.com> wrote:

> Noa,
>
> I think of one very good reason -- as of this month, Java6 has been EOL'ed
> [1] by Oracle (i.e. no more updates).  Given the number of security issues
> that have cropped in Java lately, it seems prudent, in my mind, to ensure
> that the next release runs on an officially supported JRE.  Also, OpenJDK 7
> is widely available for modern distributions (see openjdk-7 packages in
> Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).
>
> Thanks,
> -John
>
> [1]: http://www.oracle.com/technetwork/java/eol-135779.html
> On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com> wrote:
>
> > Unless someone comes with a very good argument to drop java 6
> compatibility
> > (and make a good case for it in in public and gather consensus) I would
> > consider this a bug that needs to be fixed.
> >
> > /noa
> >
> >
> > On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <
> chip.childers@sungard.com>wrote:
> >
> >> I didn't think that we agreed to bumping the java version to 7, and it
> >> seems like that might make working with distros / packages difficult.
> >>
> >> Adding Alex and Frank to the CC to get their take.
> >>
> >> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> >>> Hi,
> >>>
> >>> So the last couple of days the master branch wouldn't build on my
> >> systems:
> >>>
> >>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
> >> [1.874s]
> >>> ...
> >>> ...
> >>> [INFO]
> >> ------------------------------------------------------------------------
> >>> [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> >>> (default-compile) on project cloud-framework-ipc: Compilation
> >>> failure: Compilation failure:
> >>> [ERROR]
> >>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> >>> type parameters of <T>T cannot be determined; no unique maximal
> >>> instance exists for type variable T with upper bounds
> >>> T,java.lang.Object
> >>> [ERROR]
> >>
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> >>> type parameters of <T>T cannot be determined; no unique maximal
> >>> instance exists for type variable T with upper bounds
> >>> T,java.lang.Object
> >>>
> >>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> >>> servers) and this is the maven information:
> >>>
> >>> wido@wido-desktop:~$ mvn -v
> >>> Apache Maven 3.0.4
> >>> Maven home: /usr/share/maven
> >>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> >>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> >>> Default locale: en_US, platform encoding: UTF-8
> >>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
> >> "unix"
> >>> wido@wido-desktop:~$
> >>>
> >>> Now, that Java version is old, I know, but it's the openjdk version
> >>> which is in Ubuntu 12.04's repositories right now.
> >>>
> >>> I downloaded Java 7:
> >>>
> >>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
> >> -v
> >>> Apache Maven 3.0.4
> >>> Maven home: /usr/share/maven
> >>> Java version: 1.7.0_15, vendor: Oracle Corporation
> >>> Java home: /opt/jdk1.7.0_15/jre
> >>> Default locale: en_US, platform encoding: UTF-8
> >>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
> >> "unix"
> >>> wido@wido-desktop:~/repos/cloudstack$
> >>>
> >>> With that Java version the master branch builds just fine.
> >>>
> >>>
> >>> What I want to discuss which version of Java we support.
> >>>
> >>> I'd say we support the LTS version of any major release of CentOS or
> >> Ubuntu.
> >>>
> >>> I also understand that Java 6 is pretty old, so what do we do?
> >>>
> >>> Wido
> >>>
> >>
> >
> >
> >
> > --
> > Engineering Experience, Infrastructure tribe, Spotify
>
>


-- 
Engineering Experience, Infrastructure tribe, Spotify

Re: [DISCUSS] Supported Java version

Posted by John Burwell <jb...@basho.com>.
Noa,

I think of one very good reason -- as of this month, Java6 has been EOL'ed [1] by Oracle (i.e. no more updates).  Given the number of security issues that have cropped in Java lately, it seems prudent, in my mind, to ensure that the next release runs on an officially supported JRE.  Also, OpenJDK 7 is widely available for modern distributions (see openjdk-7 packages in Ubuntu 12.04 and java-1.7.0-openjdk in RHEL/CentOS 6.3).

Thanks,
-John

[1]: http://www.oracle.com/technetwork/java/eol-135779.html
On Feb 25, 2013, at 10:24 AM, Noa Resare <no...@spotify.com> wrote:

> Unless someone comes with a very good argument to drop java 6 compatibility
> (and make a good case for it in in public and gather consensus) I would
> consider this a bug that needs to be fixed.
> 
> /noa
> 
> 
> On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>wrote:
> 
>> I didn't think that we agreed to bumping the java version to 7, and it
>> seems like that might make working with distros / packages difficult.
>> 
>> Adding Alex and Frank to the CC to get their take.
>> 
>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>> Hi,
>>> 
>>> So the last couple of days the master branch wouldn't build on my
>> systems:
>>> 
>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>> [1.874s]
>>> ...
>>> ...
>>> [INFO]
>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>> (default-compile) on project cloud-framework-ipc: Compilation
>>> failure: Compilation failure:
>>> [ERROR]
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object
>>> [ERROR]
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object
>>> 
>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>> servers) and this is the maven information:
>>> 
>>> wido@wido-desktop:~$ mvn -v
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>> "unix"
>>> wido@wido-desktop:~$
>>> 
>>> Now, that Java version is old, I know, but it's the openjdk version
>>> which is in Ubuntu 12.04's repositories right now.
>>> 
>>> I downloaded Java 7:
>>> 
>>> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>> -v
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_15, vendor: Oracle Corporation
>>> Java home: /opt/jdk1.7.0_15/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
>> "unix"
>>> wido@wido-desktop:~/repos/cloudstack$
>>> 
>>> With that Java version the master branch builds just fine.
>>> 
>>> 
>>> What I want to discuss which version of Java we support.
>>> 
>>> I'd say we support the LTS version of any major release of CentOS or
>> Ubuntu.
>>> 
>>> I also understand that Java 6 is pretty old, so what do we do?
>>> 
>>> Wido
>>> 
>> 
> 
> 
> 
> -- 
> Engineering Experience, Infrastructure tribe, Spotify


Re: [DISCUSS] Supported Java version

Posted by Noa Resare <no...@spotify.com>.
Unless someone comes with a very good argument to drop java 6 compatibility
(and make a good case for it in in public and gather consensus) I would
consider this a bug that needs to be fixed.

/noa


On Mon, Feb 25, 2013 at 4:00 PM, Chip Childers <ch...@sungard.com>wrote:

> I didn't think that we agreed to bumping the java version to 7, and it
> seems like that might make working with distros / packages difficult.
>
> Adding Alex and Frank to the CC to get their take.
>
> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> > Hi,
> >
> > So the last couple of days the master branch wouldn't build on my
> systems:
> >
> > [INFO] Apache CloudStack Framework - IPC ................. FAILURE
> [1.874s]
> > ...
> > ...
> > [INFO]
> ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> > (default-compile) on project cloud-framework-ipc: Compilation
> > failure: Compilation failure:
> > [ERROR]
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> > type parameters of <T>T cannot be determined; no unique maximal
> > instance exists for type variable T with upper bounds
> > T,java.lang.Object
> > [ERROR]
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> > type parameters of <T>T cannot be determined; no unique maximal
> > instance exists for type variable T with upper bounds
> > T,java.lang.Object
> >
> > So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> > servers) and this is the maven information:
> >
> > wido@wido-desktop:~$ mvn -v
> > Apache Maven 3.0.4
> > Maven home: /usr/share/maven
> > Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> > Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
> "unix"
> > wido@wido-desktop:~$
> >
> > Now, that Java version is old, I know, but it's the openjdk version
> > which is in Ubuntu 12.04's repositories right now.
> >
> > I downloaded Java 7:
> >
> > wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
> -v
> > Apache Maven 3.0.4
> > Maven home: /usr/share/maven
> > Java version: 1.7.0_15, vendor: Oracle Corporation
> > Java home: /opt/jdk1.7.0_15/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family:
> "unix"
> > wido@wido-desktop:~/repos/cloudstack$
> >
> > With that Java version the master branch builds just fine.
> >
> >
> > What I want to discuss which version of Java we support.
> >
> > I'd say we support the LTS version of any major release of CentOS or
> Ubuntu.
> >
> > I also understand that Java 6 is pretty old, so what do we do?
> >
> > Wido
> >
>



-- 
Engineering Experience, Infrastructure tribe, Spotify

RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
John,

I'm not sure I understand.  Compiling with JDK6 or JDK7 with 1.6 compat mode on and running ACS on JRE7 are two different things.  I definitely think we should test with both JRE6 and JRE7 even in 4.1 and let the system admin make the decision on when to switch from JRE6 to JRE7.  However, I don't think, at this point, we should compile with JDK7 and use JDK7 only features which forces the admin's hand in upgrading from JRE6 to JRE7.

--Alex

> -----Original Message-----
> From: John Burwell [mailto:jburwell@basho.com]
> Sent: Tuesday, February 26, 2013 12:12 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Supported Java version
> 
> Alex,
> 
> Putting on my systems administrator hat, I consider security updates a
> significant, if not, vital feature.  Since Oracle will cease issuing security
> updates for Java6 at the end of this month (February 2013), I think support
> for Java7 becomes compelling if not mandatory.  Since we will not officially
> support Java7 in 4.1, our users be forced to run on an unsupported JRE for 4-
> 6 months.  The question to my mind is not whether or not Java7 is supported
> in the next major release (with Java6 deprecated), but can we provide a
> remediation sooner that would allow our users to run on a supported JRE?
> 
> Thanks,
> -John
> 
> On Feb 26, 2013, at 2:55 PM, Alex Huang <al...@citrix.com> wrote:
> 
> > I apologize for this.  I really meant popular distro versions instead of "new".
> >
> > We have to consider existing CloudStack users here.  They may want to
> update CloudStack but have an existing OS deployment that they're perfectly
> fine with and updating it means more complications in the upgrade process
> and longer downtime.  I don't think we can cease support for 6 that quickly.
> >
> > In my previous work, support for an older Java version generally ceases
> only when the newer Java version has features that we really want to use.
> For example, generics or annotations.  Is there anything Java 7 that we really
> need to use in CloudStack?
> >
> > --Alex
> >
> >> -----Original Message-----
> >> From: Joe Brockmeier [mailto:jzb@zonker.net]
> >> Sent: Tuesday, February 26, 2013 11:19 AM
> >> To: cloudstack-dev@incubator.apache.org
> >> Subject: Re: [DISCUSS] Supported Java version
> >>
> >> On Tue, Feb 26, 2013, at 12:38 PM, John Burwell wrote:
> >>> +1 to the major version bump.
> >>> On Feb 26, 2013, at 6:07 AM, Wido den Hollander <wi...@widodh.nl>
> wrote:
> >>>
> >>>> On 02/25/2013 06:36 PM, Alex Huang wrote:
> >>>>> I don't think these things are mutually exclusive.
> >>>>>
> >>>>> We should support Java7.
> >>>>> We should keep supporting Java6 until it is no longer supported by
> >>>>> the
> >> new distros.
> >>
> >> So - Oracle Java 6 is no longer supported by Ubuntu, at least, nor
> >> shipped any longer.
> >>
> >> OpenJDK 6 will wind down support this month, if I'm understanding
> >> things
> >> correctly:
> >>
> >> http://mail.openjdk.java.net/pipermail/jdk6-dev/2013-January/002835.h
> >> tml
> >>
> >> We should deprecate Java 6 in 4.2 - continue to support it, but be
> >> very loud that we are going to cease officially supporting Java 6 after 4.2.
> >> If that means we bump 4.2+1 to 5.0, then it's probably going to be
> >> time to do so.
> >>
> >> Best,
> >>
> >> jzb
> >> --
> >> Joe Brockmeier
> >> jzb@zonker.net
> >> Twitter: @jzb
> >> http://www.dissociatedpress.net/


Re: [DISCUSS] Supported Java version

Posted by John Burwell <jb...@basho.com>.
Alex,

Putting on my systems administrator hat, I consider security updates a significant, if not, vital feature.  Since Oracle will cease issuing security updates for Java6 at the end of this month (February 2013), I think support for Java7 becomes compelling if not mandatory.  Since we will not officially support Java7 in 4.1, our users be forced to run on an unsupported JRE for 4-6 months.  The question to my mind is not whether or not Java7 is supported in the next major release (with Java6 deprecated), but can we provide a remediation sooner that would allow our users to run on a supported JRE?

Thanks,
-John

On Feb 26, 2013, at 2:55 PM, Alex Huang <al...@citrix.com> wrote:

> I apologize for this.  I really meant popular distro versions instead of "new".
> 
> We have to consider existing CloudStack users here.  They may want to update CloudStack but have an existing OS deployment that they're perfectly fine with and updating it means more complications in the upgrade process and longer downtime.  I don't think we can cease support for 6 that quickly.  
> 
> In my previous work, support for an older Java version generally ceases only when the newer Java version has features that we really want to use.  For example, generics or annotations.  Is there anything Java 7 that we really need to use in CloudStack?
> 
> --Alex
> 
>> -----Original Message-----
>> From: Joe Brockmeier [mailto:jzb@zonker.net]
>> Sent: Tuesday, February 26, 2013 11:19 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] Supported Java version
>> 
>> On Tue, Feb 26, 2013, at 12:38 PM, John Burwell wrote:
>>> +1 to the major version bump.
>>> On Feb 26, 2013, at 6:07 AM, Wido den Hollander <wi...@widodh.nl> wrote:
>>> 
>>>> On 02/25/2013 06:36 PM, Alex Huang wrote:
>>>>> I don't think these things are mutually exclusive.
>>>>> 
>>>>> We should support Java7.
>>>>> We should keep supporting Java6 until it is no longer supported by the
>> new distros.
>> 
>> So - Oracle Java 6 is no longer supported by Ubuntu, at least, nor shipped any
>> longer.
>> 
>> OpenJDK 6 will wind down support this month, if I'm understanding things
>> correctly:
>> 
>> http://mail.openjdk.java.net/pipermail/jdk6-dev/2013-January/002835.html
>> 
>> We should deprecate Java 6 in 4.2 - continue to support it, but be very loud
>> that we are going to cease officially supporting Java 6 after 4.2.
>> If that means we bump 4.2+1 to 5.0, then it's probably going to be time to do
>> so.
>> 
>> Best,
>> 
>> jzb
>> --
>> Joe Brockmeier
>> jzb@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/


RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
I apologize for this.  I really meant popular distro versions instead of "new".

We have to consider existing CloudStack users here.  They may want to update CloudStack but have an existing OS deployment that they're perfectly fine with and updating it means more complications in the upgrade process and longer downtime.  I don't think we can cease support for 6 that quickly.  

In my previous work, support for an older Java version generally ceases only when the newer Java version has features that we really want to use.  For example, generics or annotations.  Is there anything Java 7 that we really need to use in CloudStack?

--Alex

> -----Original Message-----
> From: Joe Brockmeier [mailto:jzb@zonker.net]
> Sent: Tuesday, February 26, 2013 11:19 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Supported Java version
> 
> On Tue, Feb 26, 2013, at 12:38 PM, John Burwell wrote:
> > +1 to the major version bump.
> > On Feb 26, 2013, at 6:07 AM, Wido den Hollander <wi...@widodh.nl> wrote:
> >
> > > On 02/25/2013 06:36 PM, Alex Huang wrote:
> > >> I don't think these things are mutually exclusive.
> > >>
> > >> We should support Java7.
> > >> We should keep supporting Java6 until it is no longer supported by the
> new distros.
> 
> So - Oracle Java 6 is no longer supported by Ubuntu, at least, nor shipped any
> longer.
> 
> OpenJDK 6 will wind down support this month, if I'm understanding things
> correctly:
> 
> http://mail.openjdk.java.net/pipermail/jdk6-dev/2013-January/002835.html
> 
> We should deprecate Java 6 in 4.2 - continue to support it, but be very loud
> that we are going to cease officially supporting Java 6 after 4.2.
> If that means we bump 4.2+1 to 5.0, then it's probably going to be time to do
> so.
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> jzb@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Re: [DISCUSS] Supported Java version

Posted by Joe Brockmeier <jz...@zonker.net>.
On Tue, Feb 26, 2013, at 12:38 PM, John Burwell wrote:
> +1 to the major version bump.
> On Feb 26, 2013, at 6:07 AM, Wido den Hollander <wi...@widodh.nl> wrote:
> 
> > On 02/25/2013 06:36 PM, Alex Huang wrote:
> >> I don't think these things are mutually exclusive.
> >> 
> >> We should support Java7.
> >> We should keep supporting Java6 until it is no longer supported by the new distros.

So - Oracle Java 6 is no longer supported by Ubuntu, at least, nor
shipped any longer.

OpenJDK 6 will wind down support this month, if I'm understanding things
correctly:

http://mail.openjdk.java.net/pipermail/jdk6-dev/2013-January/002835.html

We should deprecate Java 6 in 4.2 - continue to support it, but be very
loud that we are going to cease officially supporting Java 6 after 4.2.
If that means we bump 4.2+1 to 5.0, then it's probably going to be time
to do so. 

Best,

jzb
-- 
Joe Brockmeier
jzb@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: [DISCUSS] Supported Java version

Posted by John Burwell <jb...@basho.com>.
+1 to the major version bump.
On Feb 26, 2013, at 6:07 AM, Wido den Hollander <wi...@widodh.nl> wrote:

> On 02/25/2013 06:36 PM, Alex Huang wrote:
>> I don't think these things are mutually exclusive.
>> 
>> We should support Java7.
>> We should keep supporting Java6 until it is no longer supported by the new distros.
>> 
> 
> +1 on that.
> 
> And what David mentions in his mail, it would be worth bumping to 5.0 for that.
> 
> Wido
> 
>> --Alex
>> 
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Monday, February 25, 2013 7:00 AM
>>> To: cloudstack-dev@incubator.apache.org
>>> Cc: Frank Zhang; Alex Huang
>>> Subject: Re: [DISCUSS] Supported Java version
>>> 
>>> I didn't think that we agreed to bumping the java version to 7, and it seems
>>> like that might make working with distros / packages difficult.
>>> 
>>> Adding Alex and Frank to the CC to get their take.
>>> 
>>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>>> Hi,
>>>> 
>>>> So the last couple of days the master branch wouldn't build on my systems:
>>>> 
>>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>>>> [1.874s] ...
>>>> ...
>>>> [INFO]
>>>> ----------------------------------------------------------------------
>>>> --
>>>> [ERROR] Failed to execute goal
>>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>>> (default-compile) on project cloud-framework-ipc: Compilation
>>>> failure: Compilation failure:
>>>> [ERROR]
>>>> 
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
>>> ou
>>>> dstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object [ERROR]
>>>> 
>>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
>>> ou
>>>> dstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>>> type parameters of <T>T cannot be determined; no unique maximal
>>>> instance exists for type variable T with upper bounds
>>>> T,java.lang.Object
>>>> 
>>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>>> servers) and this is the maven information:
>>>> 
>>>> wido@wido-desktop:~$ mvn -v
>>>> Apache Maven 3.0.4
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
>>>> version: "3.2.0-38-generic", arch: "amd64", family: "unix"
>>>> wido@wido-desktop:~$
>>>> 
>>>> Now, that Java version is old, I know, but it's the openjdk version
>>>> which is in Ubuntu 12.04's repositories right now.
>>>> 
>>>> I downloaded Java 7:
>>>> 
>>>> wido@wido-
>>> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>>>> -v Apache Maven 3.0.4 Maven home: /usr/share/maven Java version:
>>>> 1.7.0_15, vendor: Oracle Corporation Java home: /opt/jdk1.7.0_15/jre
>>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
>>>> version: "3.2.0-38-generic", arch: "amd64", family: "unix"
>>>> wido@wido-desktop:~/repos/cloudstack$
>>>> 
>>>> With that Java version the master branch builds just fine.
>>>> 
>>>> 
>>>> What I want to discuss which version of Java we support.
>>>> 
>>>> I'd say we support the LTS version of any major release of CentOS or
>>> Ubuntu.
>>>> 
>>>> I also understand that Java 6 is pretty old, so what do we do?
>>>> 
>>>> Wido
>>>> 
> 


Re: [DISCUSS] Supported Java version

Posted by Wido den Hollander <wi...@widodh.nl>.
On 02/25/2013 06:36 PM, Alex Huang wrote:
> I don't think these things are mutually exclusive.
>
> We should support Java7.
> We should keep supporting Java6 until it is no longer supported by the new distros.
>

+1 on that.

And what David mentions in his mail, it would be worth bumping to 5.0 
for that.

Wido

> --Alex
>
>> -----Original Message-----
>> From: Chip Childers [mailto:chip.childers@sungard.com]
>> Sent: Monday, February 25, 2013 7:00 AM
>> To: cloudstack-dev@incubator.apache.org
>> Cc: Frank Zhang; Alex Huang
>> Subject: Re: [DISCUSS] Supported Java version
>>
>> I didn't think that we agreed to bumping the java version to 7, and it seems
>> like that might make working with distros / packages difficult.
>>
>> Adding Alex and Frank to the CC to get their take.
>>
>> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
>>> Hi,
>>>
>>> So the last couple of days the master branch wouldn't build on my systems:
>>>
>>> [INFO] Apache CloudStack Framework - IPC ................. FAILURE
>>> [1.874s] ...
>>> ...
>>> [INFO]
>>> ----------------------------------------------------------------------
>>> --
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
>>> (default-compile) on project cloud-framework-ipc: Compilation
>>> failure: Compilation failure:
>>> [ERROR]
>>>
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
>> ou
>>> dstack/framework/rpc/RpcServerCallImpl.java:[51,58]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object [ERROR]
>>>
>> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
>> ou
>>> dstack/framework/rpc/RpcClientCallImpl.java:[191,60]
>>> type parameters of <T>T cannot be determined; no unique maximal
>>> instance exists for type variable T with upper bounds
>>> T,java.lang.Object
>>>
>>> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
>>> servers) and this is the maven information:
>>>
>>> wido@wido-desktop:~$ mvn -v
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
>>> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
>>> version: "3.2.0-38-generic", arch: "amd64", family: "unix"
>>> wido@wido-desktop:~$
>>>
>>> Now, that Java version is old, I know, but it's the openjdk version
>>> which is in Ubuntu 12.04's repositories right now.
>>>
>>> I downloaded Java 7:
>>>
>>> wido@wido-
>> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
>>> -v Apache Maven 3.0.4 Maven home: /usr/share/maven Java version:
>>> 1.7.0_15, vendor: Oracle Corporation Java home: /opt/jdk1.7.0_15/jre
>>> Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
>>> version: "3.2.0-38-generic", arch: "amd64", family: "unix"
>>> wido@wido-desktop:~/repos/cloudstack$
>>>
>>> With that Java version the master branch builds just fine.
>>>
>>>
>>> What I want to discuss which version of Java we support.
>>>
>>> I'd say we support the LTS version of any major release of CentOS or
>> Ubuntu.
>>>
>>> I also understand that Java 6 is pretty old, so what do we do?
>>>
>>> Wido
>>>


Re: [DISCUSS] Supported Java version

Posted by David Nalley <da...@gnsa.us>.
On Mon, Feb 25, 2013 at 12:36 PM, Alex Huang <Al...@citrix.com> wrote:
> I don't think these things are mutually exclusive.
>
> We should support Java7.
> We should keep supporting Java6 until it is no longer supported by the new distros.
>
> --Alex
>

I agree.
Changing requirements for something as fundamental as the version of
java is major-version-bump-worthy IMO.

--David

RE: [DISCUSS] Supported Java version

Posted by Alex Huang <Al...@citrix.com>.
I don't think these things are mutually exclusive.

We should support Java7.
We should keep supporting Java6 until it is no longer supported by the new distros.

--Alex

> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Monday, February 25, 2013 7:00 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Frank Zhang; Alex Huang
> Subject: Re: [DISCUSS] Supported Java version
> 
> I didn't think that we agreed to bumping the java version to 7, and it seems
> like that might make working with distros / packages difficult.
> 
> Adding Alex and Frank to the CC to get their take.
> 
> On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> > Hi,
> >
> > So the last couple of days the master branch wouldn't build on my systems:
> >
> > [INFO] Apache CloudStack Framework - IPC ................. FAILURE
> > [1.874s] ...
> > ...
> > [INFO]
> > ----------------------------------------------------------------------
> > --
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> > (default-compile) on project cloud-framework-ipc: Compilation
> > failure: Compilation failure:
> > [ERROR]
> >
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> ou
> > dstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> > type parameters of <T>T cannot be determined; no unique maximal
> > instance exists for type variable T with upper bounds
> > T,java.lang.Object [ERROR]
> >
> /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cl
> ou
> > dstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> > type parameters of <T>T cannot be determined; no unique maximal
> > instance exists for type variable T with upper bounds
> > T,java.lang.Object
> >
> > So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> > servers) and this is the maven information:
> >
> > wido@wido-desktop:~$ mvn -v
> > Apache Maven 3.0.4
> > Maven home: /usr/share/maven
> > Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> > Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> > Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> > version: "3.2.0-38-generic", arch: "amd64", family: "unix"
> > wido@wido-desktop:~$
> >
> > Now, that Java version is old, I know, but it's the openjdk version
> > which is in Ubuntu 12.04's repositories right now.
> >
> > I downloaded Java 7:
> >
> > wido@wido-
> desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn
> > -v Apache Maven 3.0.4 Maven home: /usr/share/maven Java version:
> > 1.7.0_15, vendor: Oracle Corporation Java home: /opt/jdk1.7.0_15/jre
> > Default locale: en_US, platform encoding: UTF-8 OS name: "linux",
> > version: "3.2.0-38-generic", arch: "amd64", family: "unix"
> > wido@wido-desktop:~/repos/cloudstack$
> >
> > With that Java version the master branch builds just fine.
> >
> >
> > What I want to discuss which version of Java we support.
> >
> > I'd say we support the LTS version of any major release of CentOS or
> Ubuntu.
> >
> > I also understand that Java 6 is pretty old, so what do we do?
> >
> > Wido
> >

Re: [DISCUSS] Supported Java version

Posted by Chip Childers <ch...@sungard.com>.
I didn't think that we agreed to bumping the java version to 7, and it
seems like that might make working with distros / packages difficult.

Adding Alex and Frank to the CC to get their take.

On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> Hi,
> 
> So the last couple of days the master branch wouldn't build on my systems:
> 
> [INFO] Apache CloudStack Framework - IPC ................. FAILURE [1.874s]
> ...
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile
> (default-compile) on project cloud-framework-ipc: Compilation
> failure: Compilation failure:
> [ERROR] /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcServerCallImpl.java:[51,58]
> type parameters of <T>T cannot be determined; no unique maximal
> instance exists for type variable T with upper bounds
> T,java.lang.Object
> [ERROR] /home/employee/wido/repos/cloudstack/framework/ipc/src/org/apache/cloudstack/framework/rpc/RpcClientCallImpl.java:[191,60]
> type parameters of <T>T cannot be determined; no unique maximal
> instance exists for type variable T with upper bounds
> T,java.lang.Object
> 
> So I'm running Ubuntu 12.04.1 on all my systems (laptop, desktop,
> servers) and this is the maven information:
> 
> wido@wido-desktop:~$ mvn -v
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.6.0_27, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family: "unix"
> wido@wido-desktop:~$
> 
> Now, that Java version is old, I know, but it's the openjdk version
> which is in Ubuntu 12.04's repositories right now.
> 
> I downloaded Java 7:
> 
> wido@wido-desktop:~/repos/cloudstack$ JAVA_HOME="/opt/jdk1.7.0_15" mvn -v
> Apache Maven 3.0.4
> Maven home: /usr/share/maven
> Java version: 1.7.0_15, vendor: Oracle Corporation
> Java home: /opt/jdk1.7.0_15/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.2.0-38-generic", arch: "amd64", family: "unix"
> wido@wido-desktop:~/repos/cloudstack$
> 
> With that Java version the master branch builds just fine.
> 
> 
> What I want to discuss which version of Java we support.
> 
> I'd say we support the LTS version of any major release of CentOS or Ubuntu.
> 
> I also understand that Java 6 is pretty old, so what do we do?
> 
> Wido
> 

Re: [DISCUSS] Supported Java version

Posted by Chip Childers <ch...@sungard.com>.
On Mon, Feb 25, 2013 at 12:23:39PM +0100, Wido den Hollander wrote:
> Hi,
> 
> So the last couple of days the master branch wouldn't build on my systems:

Is this a problem on the 4.1 branch as well?  Do you mind checking it?