[Engine-devel] java 1.6 compatibility no more?

[Itamar Heim]

On 07/18/2012 08:21 PM, Juan Hernandez wrote:
> On 07/18/2012 06:33 PM, Vojtech Szocs wrote:
>> In fact, for both backend and frontend, Maven effective POM contains:
>>
>> <artifactId>maven-compiler-plugin</artifactId>
>> <configuration>
>>    <source>1.6</source>
>>    <target>1.6</target>
>> </configuration>
>>
>> Therefore, according to Maven POM files, oVirt should be build-able using Java 6, but it's not. (?)
>
> These maven settings just tell the java compiler to accept Java 6 syntax
> only and to generate a Java 6 compatible .class file format, but they
> don't restrict the set of APIs that can be used.

I think the question is if it makes any sense to keep/force java 6 
compatibility for next version of ovirt, with java 6 EOL dates.

a jenkins job compiling for java 6 compatibility is easy to create - 
question is if there is a reason to do it.

>
>> The problem is in backend/manager/modules/bll: StorageDomainCommandBase class uses new Java 7 Long.compare() static method.
>>
>> I think we should decide if we want to be compliant with Java 7, or submit a patch that uses Java 6 API (Long.compareTo instance method).
>>
>> Vojtech
>>
>>
>> ----- Original Message -----
>> From: "Laszlo Hornyak" <lhornyak at redhat.com>
>> To: "engine-devel" <engine-devel at ovirt.org>
>> Cc: "Vojtech Szocs" <vszocs at redhat.com>
>> Sent: Wednesday, July 18, 2012 5:43:34 PM
>> Subject: java 1.6 compatibility no more?
>>
>> Hi,
>>
>> It may be a historic moment, but for a few hours oVirt engine is no longer building on java 1.6.
>> Is this intentional?
>>
>> Laszlo
>> _______________________________________________
>> Engine-devel mailing list
>> Engine-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/engine-devel
>>
>
>