I think this makes sense. We waited too long to drop support for Java 5, lets not repeat that with 6. Beginning to depend on Java 7 after three years doesnt seem unreasonable to me.
Those those who 'cant' or dont want to upgrade to such 'new' (i.e really quite old now) Java releases are often likely to be the same ones that aren't so likely to use the latest Qpid releases either. Robbie On 7 April 2014 13:17, Rob Godfrey <[email protected]> wrote: > All, > > now that Java 8 has been released, and Java 6 has been officially EOLd for > well over a year, I'd like to propose that we make 0.28 the last release > for which we officially support Java 6. As a library provider I'm aware > that we need to strive to make our libraries as widely adoptable as > possible, but not adopting Java 7 also holds us back from implementing > functionality that requires features of later releases (as JMS 2.0 does). > > Java 7 was released in 2011 and is itself scheduled to be EOLd next year. > > If we do later find critical defects that affect the 0.28 release we should > consider back-patching to a Java 6 release based on 0.28, however I don't > think requiring that all new functionality releases require the adoption a > version of Java that Oracle supports to be an undue burden. > > -- Rob >
