i cant believe that..java 6 is already out for years.. they are already at update 17.. java 5 was sep 2004! java 6 dec 2006
thats already 3 years ago.. I cant beleive that there are many still on java 5 they really should upgrade because java 6 didnt maybe bring much api wise but performance wise it was quite a good jump. Besides that when wicket 1.5 will be released we will be i guess at least half next year then java 7 is almost there. (i think... java 7 is just a bit question mark) On Tue, Dec 15, 2009 at 12:36, Carl-Eric Menzel < cm.wic...@users.bitforce.com> wrote: > On Tue, 15 Dec 2009 11:44:23 +0100 > Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > > > I was going to propose a vote in that direction... as JDK 1.5 has been > > shelved... > > > > It'll be years until Java 1.6 is as common as 1.5 is now. There are many > organizations who have only just completed the move to 1.5. I think > going to a strict requirement for Java 1.6 would be a really bad idea, > especially since it does not offer as many significant new benefits as > 1.5 did. > > Offering 1.6-specific features in a separate jar would be a simple and > pretty good solution, I think. Stuff like the typesafe model would thus > be available for those who need it, without leaving anybody needlessly > stranded. > > Carl-Eric >
