Not sure if forcing 1.6 is really required. Does that bring any value ? Another way is does that even change anything for us ?
On Wed, Nov 9, 2011 at 15:16, Jamie G. <[email protected]> wrote: > The concept of a 2.3.x branch to bridge the differences between 2.2.x > and the to be 3.0.0 makes sense from the point of view of providing > our user base an easier transition. I would like to know if we intend > to keep JDK 1.5 compatibility on 2.3.x or if we'll have to enforce an > update to JDK 1.6? > > Cheers, > Jamie > > On Wed, Nov 9, 2011 at 7:24 PM, Jean-Baptiste Onofré <[email protected]> > wrote: > > Hi all, > > > > we started to perform a bunch of changes on the Karaf trunk (future Karaf > > 3.0 branch): refactoring on the commands to introduce the sub-shell, > update > > to Pax Web 2.0 and Jetty 8, renaming on the commands, new OSGi release, > new > > Aries version, etc. > > > > It means a huge change for the users. > > > > As our Karaf 2.2.x branch is our current stable branch, Guillaume and I > > discussed the creation of a Karaf 2.3.x branch (waiting the 3.0 release). > > > > This branch will include "minor" new features and dependencies upgrade. > > > > Especially, I think it could be interesting to do on this branch: > > - new OSGi release and framework update > > - Aries update > > - scp support and others minor new features > > > > WDYT ? > > > > Thanks > > Regards > > JB > > -- > > Jean-Baptiste Onofré > > [email protected] > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
