[infinispan-dev] Baselining on Java 7

[Bela Ban]

On 5/23/13 1:11 PM, Sanne Grinovero wrote:
> WildFly already requires Java7.


OK. This doesn't mean though that JGroups 4 has to require JDK 7; it can 
still baseline on JDK 6. As long as
jgroups version <= infinispan version <= wildfly version
, we're fine. Of course, we can always link to a module requiring a 
higher JDK than the component consuming us *dynamically*


> Hibernate Search will likely stay a bit longer on 6, and depends on
> Infinispan, but this dependency is an isolated module so we can live
> with it by making our build a bit more painful. Users would then need
> Java7 only if they want to use the Infinispan extensions.
>
> Sanne
>
> On 23 May 2013 12:06, Bela Ban <bban at redhat.com> wrote:
>>
>>
>> On 5/23/13 12:38 PM, Manik Surtani wrote:
>>> Yup, it needs to happen sometime.  But the question is, when?
>>>
>>> Is there anyone out there who desperately needs Infinispan to work on Java 6?
>>
>> I got a lot of pushback when I moved the required JDK in JGroups to 1.5
>> (people were still using 1.4), and the same for moving from 1.5 to 1.6,
>> so I anticipate this won't be different for moving to 1.7 as baseline.
>>
>> I personally would not mind waiting for JGroups 5 to move to JDK 7, as
>> this gives users a bit more time and I won't require JDK 7 before
>> JGroups 5 anyway, as the NIO2 stuff won't be in JGroups 4, only in 5.
>>
>> But if you guys need to move to JDK 7 in Infinispan 6 already, then
>> that's fine with me, too.
>>
>> I guess the AS has some requirements, too, so if they decide to move to
>> JDK 7, then we'll have to make that move too

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)