No, because we want 1.4 and 1.3 to remain largely compatible. having to maintain 2 sets of tests is a drag.
Martijn On Thu, Oct 9, 2008 at 11:58 PM, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > Afaik JUnit 4 is fully backwards compatible. So you could just switch, > and start using JUnit 4 features when working on tests anyway. > > Jörn > > On Thu, Oct 9, 2008 at 11:52 PM, Martijn Dashorst > <[EMAIL PROTECTED]> wrote: >> Wicket 1.5 might move to junit 4 when we take a closer look at wicket >> tester. Before that we'd rather concentrate on stabilizing wicket >> itself. There's little benefit in changing our tests just to upgrade >> to junit 4. >> >> Martijn >> >> On Thu, Oct 9, 2008 at 10:25 PM, Antony Stubbs <[EMAIL PROTECTED]> wrote: >>> Has there been any conversation about upgrading to Junit 4 or possibly >>> migrating to TestNG? >>> I've done a search on it but haven't found any. >>> >>> Cheers. >>> ___________________________ >>> http://stubbisms.wordpress.com/ >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.4 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
