On 26 Sep 2009, at 18:29, Adrian Cole wrote:
I think most enterprises will react to the EOL of JDK 5. For
example, when JDK 1.4 was EOL, almost all applications in a medium
sized enterprise I worked in were on JDK 5 within a year. One
limiting factor in uptake time was the maturity of appservers that
supported the new JDK. In today's context, JDK 6 compatible
appservers and frameworks have been available for over a year
already, and past their .0 release. I agree that embracing
infinispan would imply reasonably fresh thinking and already place
it into a dev team who are probably already on JDK 6. I moreover
doubt any enterprise would issue a policy enforcing use of an EOL
JDK, so these fresh thinking dev teams will not likely encounter
problems moving to prod.
You're only saying that coz you want JClouds to baseline on JDK6 as
well. ;)
Lots of good sense in Sanne's and Adrian's arguments though. Anyone
else? Anybody standing on the side of JDK 5?
at the end of that ramble....
+1 release with JDK 6+ support
Cheers,
Adrian
jclouds
On Sat, Sep 26, 2009 at 5:57 AM, Sanne Grinovero <sanne.grinovero(a)gmail.com
> wrote:
My 2c:
I'm deploying only on JDKs >=6 since three years now,
and IMHO new projects going to consider Infinispan in this timeframe
are probably in a design/early development fase, almost everyone
will be ready to deploy something stable only after the JDK5 will be
phased out.
The main "market" for this kind of libraries is enterprise, which
wants support
and will probably refrain from using Java5, at least for new
deployments.
2009/9/26 Manik Surtani <manik(a)jboss.org>:
>
> On 25 Sep 2009, at 16:56, Galder Zamarreno wrote:
>
>>
>>
>> On 09/25/2009 05:38 PM, David M. Lloyd wrote:
>>> On 09/25/2009 07:38 AM, Manik Surtani wrote:
>>>> On 25 Sep 2009, at 11:53, Galder Zamarreno wrote:
>>>>> On 09/24/2009 12:50 PM, Manik Surtani wrote:
>>>>>>
>>>>>> </snip>
>>>>>>
>>>>>> For a basic runtime, the deps are fairly limited (JTA
interfaces,
>>>>>> JGroups, JBoss Marshalling if you are using JDK6. Add JAXB if
>>>>>> JDK5)
>>>>>
>>>>> Hmmm, JBoss Marshalling if you are using JDK6? JBoss
Marshalling is
>>>>> there regardless AFAIK and has JDK5 requirements. It's XNIO 2.0
>>>>> that
>>>>> might have JDK6 requirement but it'd be in an optional module
>>>>> anyway.
>>>>
>>>> I should have added brackets. :-)
>>>>
>>>> "{JTA interfaces, JGroups, JBoss Marshalling} if you are using
JDK6.
>>>> Add JAXB if JDK5."
>>>
>>> Also it seems foregone that a (relatively-near) future JBMAR will
>>> require
>>> JDK6, namely to add support for optimized serialization of new
>>> collection
>>> types and to take advantage of the faster classloading of JDK6-
>>> targeted
>>> classes.
>>
>> Hmmm, this is important since JBMAR is a core dependency. We had a
>> discussion a while back and the agreement was to stay on JDK5
since we
>> did nothing JDK6 specific but I think it might be time to move to
JDK6
>> fully, thoughts?
>
> Vote to the public? I'd love to baseline on JDK6. But I'd hate to
> limit uptake.
>
> Cheers
> --
> Manik Surtani
> manik(a)jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
>
http://www.infinispan.org
>
http://www.jbosscache.org
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org