+1, Java 1.6 on Karaf 3.x series.
2011/1/6 Łukasz Dywicki <[email protected]>: > Hi, > Than we agree that we may switch to JVM 1.6 after 3.0 release. I am happy to > hear this. :) > > Best regards, > Lukasz > > > > -----Original Message----- > From: Ioannis Canellos [mailto:[email protected]] > Sent: Thursday, January 06, 2011 9:50 AM > To: [email protected]; [email protected] > Subject: Re: Switch to Java 1.6? > > +1 > > 2011/1/6 Jean-Baptiste Onofré <[email protected]> > >> For the Karaf 2.x, I think that it's clear that we need to be JDK 1.5 >> compatible. >> >> On the other hand, for Karaf 3.x, no problem at all, +1 to be only JDK 1.6 >> compliant. >> >> Regards >> JB >> >> >> On 01/04/2011 11:08 PM, Łukasz Dywicki wrote: >> >>> Hi all, >>> >>> Some time ago I created issue KARAF-328 which is sticky card about JVM >>> version policy. >>> >>> >>> >>> Now I am a bit confused because I would like get rid XML parsing from >>> feature service and switch it to JAXB while working on KARAF-53. I know >>> that >>> build is made on JVM 1.5 and this change will broke capability with older >>> virtual machines. I wouldn't force anyone to upgrade but moving to new > JVM >>> version can simplify our life a bit. :-) >>> >>> >>> >>> Note that CXF, ActiveMQ and Camel works with Java 1.5. We have JRE 1.5 > and >>> JRE 1.6 profiles in jre.properties. From my point of view it is not a >>> problem to stay with 1.5 but if it make sense to stay with version which >>> is >>> supported only if you pay Oracle for? As another note - JVM 1.5 was >>> released >>> in May 2004 and it is 6 year old. What do you think about that? >>> >>> >>> >>> Best regards, >>> >>> Lukasz >>> >>> >>> > > > -- > *Ioannis Canellos* > http://iocanel.blogspot.com > > Integration Engineer @ Upstream S.A. <http://www.upstreamsystems.com> > >
