Re: JUnitShell: Why is the log level overriden to WARN?

2013-06-18 Thread Thomas Broyer


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 your custom RunStyle: -Dgwt.args="-logLevel DEBUG 
> -out www-test -runStyle com.example.PhantomJS:/path/to/phantomjs"
>  
>
> Hmm, I already tried setting the logLevel through the maven configuration:
> https://github.com/neothemachine/KineticGWT/blob/master/pom.xml#L122
>
> Am I doing something wrong?
>

No, the gwt-maven-plugin is doing something wrong: it does not allow you to 
configure the logLevel: 
https://github.com/gwt-maven-plugin/gwt-maven-plugin/blob/2fa0f0065aecde5e6ced88eb5f82a6e914ec2cdb/src/main/java/org/codehaus/mojo/gwt/shell/TestMojo.java#L300

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.




Re: JUnitShell: Why is the log level overriden to WARN?

2013-06-18 Thread Maik Riechert

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 
com.example.PhantomJS:/path/to/phantomjs"


Hmm, I already tried setting the logLevel through the maven configuration:
https://github.com/neothemachine/KineticGWT/blob/master/pom.xml#L122

Am I doing something wrong?

--
You received this message because you are subscribed to the Google Groups "Google 
Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.




Re: JUnitShell: Why is the log level overriden to WARN?

2013-06-18 Thread Thomas Broyer


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 
> anything. This is caused by the following code in JUnitShell I guess:
>
>   // Override log level to set WARN by default..
>   registerHandler(new ArgHandlerLogLevel(options) {
> @Override
> protected Type getDefaultLogLevel() {
>   return TreeLogger.WARN;
> }
>   });
>
> My question is: Why? I find it very strange that I can't set a custom log 
> level via command line argument or system property. What is the reasoning 
> behind this and can it be changed?
>

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 com.example.PhantomJS:/path/to/phantomjs"

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.




JUnitShell: Why is the log level overriden to WARN?

2013-06-17 Thread Maik Riechert
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:

  // Override log level to set WARN by default..
  registerHandler(new ArgHandlerLogLevel(options) {
@Override
protected Type getDefaultLogLevel() {
  return TreeLogger.WARN;
}
  });

My question is: Why? I find it very strange that I can't set a custom log 
level via command line argument or system property. What is the reasoning 
behind this and can it be changed?

Cheers
Maik

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.