* Juergen Donnerstag:
It passed all tests when I committed it. Whatever made the
test now failing, might not be related to the backport. Your
modification now definitely changed the bahavor and you are sure
that is what you intended to do?
I'm sure that it fixes markup reloading
looks more like a testcase failure itself to me.
Shouldn't the test case make the application and set in in the thread local
before it does a call that want to construct wicket things?
johan
On 4/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
There's a testing failing in Wicket examples
I think Johan is right.
Unfortunately I'm not able to look into it over the weekend since my
computer broke down yesterday and I won't get it fixed before Tuesday
next week.
I haven't maintained the example testcases for a while due to various
problem with jwebunit, javascript, etc. The whole
A related issue: template reloading from sources does not work
anymore since Localizer backport in rev 522181. I fixed this in
rev 526432, please have a look.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Does Bamboo run the example
tests as well? If yes, than the exception may be due to some other
changes.
I'm afraid the bamboo errors have to do with something else. All tests
(at least from the Wicket core project) run fine in both Eclipse and
maven. I think Bamboo is messed up somehow. See
There's a testing failing in Wicket examples currently. Is that due to
the recent refactorings?
Stacktrace:
wicket.WicketRuntimeException: There is no application attached to
current thread main
at wicket.Application.get(Application.java:167)
at
