Stick for now to Java 6 or does somebody really has good reason (api or feature that he wants to use) to go to Java 7? I think java 7 almost brought nothing, the all postponed the nice stuff to Java 8 (which is postponed to next year i believe)
i do think that the eol of java 6 is quite fast, i don't think java 7 is used a lot at all, i think even the latest ubuntu that i installed yesterday does still by default get java 6? on the mac its also still java 6 right? But i guess for November this could all change, a bit offtopic, but i like to rant: i am currently using java 7u4 and i am quite annoyed by this bug; http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7145592 so a git repo over https with self signed certificates is not going to work for EGit ..... johan On Thu, Feb 16, 2012 at 17:06, Martijn Dashorst <[email protected]>wrote: > With Oracle stopping support for Java 6 this year [1], should we > target Java 7 instead in Wicket 6? Or leave that for Wicket 7? > > I'm for keeping Java 6 as our current platform for Wicket 6 (so we > don't add to the confusion with numbering our releases). Wicket 7 can > then be our Java 7 release, and Wicket 8 our Java 8 release :). > Intermitted we can release 6.1 and such in accordance with semver and > provide new functionality in those .y releases. > > Martijn, tossing this in front of the wolves :) > > [1] https://blogs.oracle.com/henrik/entry/updated_java_6_eol_date >
