There are some API things that are better in 1.6, and not compatible with the 1.5 API, but they all seem to have some sort of work around. For some of those things we'll get better performance and maybe better flexibility (and maybe less code to maintain) if we use the 1.6 API.
IMO the biggest reason to require 1.6 is that some of the libraries we use are starting to require 1.6 for their newer versions, and chances are that will happen more over time. In other words, sooner or later we'll want to update something and they won't offer a 1.5 compatible alternative any more. -David On Nov 23, 2009, at 2:16 PM, Scott Gray wrote: > I'm not necessarily against it but I'm yet to hear what we actually gain by > doing so, what are these changes that we could optionally make once we stop > supporting 1.5? With the change from 1.4 to 1.5 it was pretty clear because > of things like generics. > > Regards > Scott > > HotWax Media > http://www.hotwaxmedia.com > > On 24/11/2009, at 9:49 AM, David E Jones wrote: > >> >> OFBiz already runs fine on 1.6, so this would just be a matter of updating >> documentation and such, and then people could optionally make changes that >> require 1.6. >> >> If everyone is in favour of this, we might as well get a vote going... >> >> -David >> >> >> On Nov 23, 2009, at 11:20 AM, Erwan de FERRIERES wrote: >> >>> +1 >>> >>> Furthermore, on a debian lenny server, there is no jdk 1.5 in the >>> repository... >>> >>> So, in order to make this migration, what are the required steps ? How can >>> we divide the work to be done ? >>> >>> Cheers >>> >>> Le 14/11/2009 05:44, Tim Ruppert a écrit : >>> ../.. >>> >>> -- >>> Erwan >> >
