Martijn Dashorst wrote:
You don't do anything wrong.In Wicket development (on the core project), the unit tests sometimes just don't run for a couple of days because they are used as a method of communication: someone knows how to reproduce a bug but doesn't know how to fix it. The unit test exposing the bug is then committed, so that someone else can look at it in due time.
FWIW, this is http://issues.apache.org/jira/browse/WICKET-590 Al
