Could someone please take a look at what's wrong with Wicket 2.0's unit tests? Besides the fact that we have 5 failures and 2 errors, they generate an enormous amount of serialization errors.
Eelco
Could someone please take a look at what's wrong with Wicket 2.0's unit tests? Besides the fact that we have 5 failures and 2 errors, they generate an enormous amount of serialization errors.
Eelco