On 3/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 3/14/07, Anders Peterson <[EMAIL PROTECTED]> wrote: > > Make one last release for JDK 1.4 and after that it's bug fixing only. > > All new development should target Java5. Wicket should have moved to > > Java5 at least one year ago!
I beg to differ. Though I only use Java 1.5 on our internal projects, I know several companies that require the use of Java 1.4, at least for now. I would not have liked it when we lost those companies. > As for dropping < JDK 1.5 support: I think the committers would love > that, but it would bring a bunch of users in trouble I'm afraid. Maybe > we should have a poll about that. I think that is a good idea. I would welcome Wicket 1.3 to be the last JDK 1.4 version. It is pretty much a vast improvement over 1.2 and contains enough features to make 1.4 people happy for a long time I think. Maintaining Wicket 1.3 should be for bug fixes, not new features. But that doesn't prevent new components to be developed, or backported by our community if there is a need for JDK 1.4 components. And if you really have a need, then you can always use retrotranslator/weaver to backport 1.5 for your own pleasure. Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
