Re: [Codenarc-developer] Reducing Build Output

[<chr...@wa...>]

I changed the test output (back) to INFO level deliberately because I am 
used to and prefer having that test output visible when I run the tests. 
But habit should not get in the way of practicality. :->  You can go ahead 
and set the test output (i.e., the log() method) to DEBUG level. I guess 
if/when I need to examine that output I can temporarily change the 
"log4j.properties" file.

>> Also, a few of the main() methods use println. Is this on purpose?

Yes, that was on purpose, but I'm not sure I can make an effective case 
for why output from a main() should be different. Feel free to change, 
otherwise I'll plan to do that.

Chris
Hamlet DArcy <ham...@ca...> wrote on 03/01/2011 02:55:08 AM:

> Hi Chris, 
> 
> Our build is very verbose. 
> 
> Do you mind if I reduce some UnitTest related warnings and info 
> messages to debug? I will leave the Logger.warn() calls in the code,
> but in unit tests I'll just redirect them to Logger.debug(). What do
> you think? 
> 
> Also, a few of the main() methods use println. Is this on purpose? 
> Or should we switch those to use Log4j info messages? 
> 
> --
> Hamlet D'Arcy
> ham...@ca...
> 
> 
> 
------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data 
in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT 
data 
> generated by your applications, servers and devices whether physical, 
virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> Codenarc-developer mailing list
> Cod...@li...
> https://lists.sourceforge.net/lists/listinfo/codenarc-developer

> ForwardSourceID:NT00104536