Re: Where does Wickets debug-output when running tests in Gradle come from?

2020-04-01 Thread Thorsten Schöning
Guten Tag Thorsten Schöning, am Mittwoch, 1. April 2020 um 11:46 schrieben Sie: >> 11:34:01.536 [Test worker] INFO org.apache.wicket.Application - >> [WicketTesterApplication-7fefbf5f-492f-4c7d-b276-522938b3242c] init: >> org.wicketstuff.event.annotation.Initializer@3456cd50 >> 11:34:01.546

Re: Where does Wickets debug-output when running tests in Gradle come from?

2020-04-01 Thread Thorsten Schöning
Guten Tag Thorsten Schöning, am Mittwoch, 1. April 2020 um 11:46 schrieben Sie: >> 11:34:01.536 [Test worker] INFO org.apache.wicket.Application - >> [WicketTesterApplication-7fefbf5f-492f-4c7d-b276-522938b3242c] init: >> org.wicketstuff.event.annotation.Initializer@3456cd50 >> 11:34:01.546

Where does Wickets debug-output when running tests in Gradle come from?

2020-04-01 Thread Thorsten Schöning
Hi all, I'm using Gradle and recently started to run tests using Wicket rendering some contents. Things work pretty well, but Wicket provides a lot of DEBUG-output on STDOUT or STDERR, which Gradle puts into its own HTML-reports for results of tests. This makes those reports pretty large in my