I'm curious - why are 3 different versions of Wicket (1.2.x, 1.3.x, & 2.x) being worked on? Isn't that a burden compared to focusing on two? When will the 1.2.x line be let go?
Thanks, Jon On 12/9/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All, We have several fixes in for 1.2.4, and one still open. When can we release 1.2.4? Bug [WICKET-29] - javascript error in wicket-ajax.js: Wicket.Log.Error is not a function [WICKET-31] - Wrong source paths in build.xml [WICKET-35] - WicketTester doesn't pass PageParameters to bookmarkable pages [WICKET-64] - Check/Radio fail in a GridView with item reuse strategy [WICKET-143] - [PATCH]Re-render a table element via AjaxRequestTarget under IE does not works [WICKET-144] - wrong handling of exceptions for Resource#respond and ComponentResourceRequestTarget#respond WICKET-144 is still unresolved. Are there other things that need fixing in 1.2.4? Martijn -- Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket Wicket 1.2.3 is as easy as 1-2-3. Download Wicket now! http://wicketframework.org
