On Monday, June 17, 2013 10:54:16 PM UTC+2, Maik Riechert wrote:
Hi,
when developing JUnit runstyles I want to do info/trace logging, e.g.:
shell.getTopLogger().log(TreeLogger.TRACE, Letting PhantomJS fetch +
url);
I have to change all those logging outputs to at least WARN to see
Thomas Broyer wrote:
You definitely *can* change the log level from the command line, WARN
is just the default value.
Arguments are passed to JUnitShell through the gwt.args system
property, the same you use to set your custom RunStyle:
-Dgwt.args=-logLevel DEBUG -out www-test -runStyle
On Tuesday, June 18, 2013 10:11:57 AM UTC+2, Maik Riechert wrote:
Thomas Broyer wrote:
You definitely *can* change the log level from the command line, WARN is
just the default value.
Arguments are passed to JUnitShell through the gwt.args system property,
the same you use to set
Hi,
when developing JUnit runstyles I want to do info/trace logging, e.g.:
shell.getTopLogger().log(TreeLogger.TRACE, Letting PhantomJS fetch +
url);
I have to change all those logging outputs to at least WARN to see
anything. This is caused by the following code in JUnitShell I guess:
