namgk / ambienttalk

Automatically exported from code.google.com/p/ambienttalk
0 stars 0 forks source link

Changing logging default priority to be 'silent' #46

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
In Eclipse plugins the Console typically shows stdout and sterror messages. 
Since AmbientTalk logs statements are printed to the System.err, the console 
gets polluted with interpreter log statements.

A good enhancement for the plugin would be that the default priority for AT 
logging is set to FATAL, and then we add an iat option that allows users to set 
the priority to lower levels when launching iat if they want the logs. 

This means that "regular" plugin users (e.g. students) will not get the 
interpreter logs in the Console, while the "advance" plugin users (e.g. 
language developers) can set an appropriate logging level when launching iat 
(without having to modify the props file).

Original issue reported on code.google.com by egonzal...@gmail.com on 13 Dec 2010 at 1:16

GoogleCodeExporter commented 8 years ago
The trunk includes since revision r2625 a -l option in iat which allows you to 
customize the default logging properties for interpreter execution which will 
be launched. 

See more info at http://code.google.com/p/ambienttalk/wiki/CommandLineParameters

Original comment by ambientt...@gmail.com on 22 Dec 2010 at 2:28

GoogleCodeExporter commented 8 years ago

Original comment by egonzal...@gmail.com on 22 Dec 2010 at 2:30