[gwt-contrib] Re: Logging not working anymore in GWT 2.7.0 RC

2015-01-06 Thread peter . leong
FWIW, I added the following properties to my module Xxx.gwt.xml config to 
get old logging back...

set-property name=gwt.logging.enabled value=TRUE/
set-property name=gwt.logging.consoleHandler value=ENABLED/
set-property name=gwt.logging.logLevel value=INFO/


This is in addition to inheriting the *com.google.gwt.logging.Logging* 
module.


On Thursday, November 20, 2014 7:15:16 PM UTC+10, Jan Thewes wrote:

 Hey guys,

 we've a problem with logging since testing GWT 2.7.
 We're using java.util.Logger() and with 2.7 any message trying to be 
 logged with WARN or lower doesn't end up in the browser console.

 What I found out is that my Logger.info(String message) call is thrown 
 away by the GWT compiler?
 Why does this happen?

 What do I have to do to  get the old behavior?

 Cheers,
 Jan


-- 
You received this message because you are subscribed to the Google Groups GWT 
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ea9fa29c-7526-43ed-8d6d-393983c8a744%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] Re: Logging not working anymore in GWT 2.7.0 RC

2014-11-20 Thread Andrei Korzhevskii
GWT 2.7 changed property value gwt.logging.enabled from TRUE to 
SEVERE (in Logging.gwt.xml) so by default app logs errors only.
To get back to pre-2.7 logging behavior, set this property to TRUE or 
WARNING (if you want to log warnings and errors).

On Thursday, November 20, 2014 12:15:16 PM UTC+3, Jan Thewes wrote:

 Hey guys,

 we've a problem with logging since testing GWT 2.7.
 We're using java.util.Logger() and with 2.7 any message trying to be 
 logged with WARN or lower doesn't end up in the browser console.

 What I found out is that my Logger.info(String message) call is thrown 
 away by the GWT compiler?
 Why does this happen?

 What do I have to do to  get the old behavior?

 Cheers,
 Jan


-- 
You received this message because you are subscribed to the Google Groups GWT 
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/bc407279-a9b3-4434-a970-bd0e71859338%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] Re: Logging not working anymore in GWT 2.7.0 RC

2014-11-20 Thread Mohammed
see below,

   - 
   
   GWT apps that inherit the com.google.gwt.logging.Logging module have 
   different default behavior for messages logged using the 
   java.util.logging package. The new default is to log messages at level 
   SEVERE and above to the browser's console. PopupLogHandler and 
   SystemHandler are no longer enabled by default.
   

On Thursday, November 20, 2014 2:45:16 PM UTC+5:30, Jan Thewes wrote:

 Hey guys,

 we've a problem with logging since testing GWT 2.7.
 We're using java.util.Logger() and with 2.7 any message trying to be 
 logged with WARN or lower doesn't end up in the browser console.

 What I found out is that my Logger.info(String message) call is thrown 
 away by the GWT compiler?
 Why does this happen?

 What do I have to do to  get the old behavior?

 Cheers,
 Jan


-- 
You received this message because you are subscribed to the Google Groups GWT 
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/ace00a95-1ee1-4d1e-a449-9333ad21a708%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.