I wrapped every print call I could find into two methods (one for
Sytem.out and one for System.err) so we can at least turn them off. I'm
actually OK just deleting them all and then just mandating that if you
want that output to use the logger but this at least cleans it up a
bit. If everyone just wants them gone, i can happily do a mass delete
now that the hard part of tracking them all down is done.
On 4/21/10 3:08 PM, Oleksiy Stashok wrote:
> Yeah those things are asking to be sort out for a long time. Some
> tests use logger, some system.out, I saw even system.err.
>
> +1
>
> WBR,
> Alexey.
> On Apr 21, 2010, at 22:34 , Justin Lee wrote:
>
>> How do people feel about all the output in the unit tests? For my
>> taste, I think they're entirely too chatty. I'm trying to
>> parameterize the display configuration setting. It'll be off by
>> default but you can turn it on if you want to see/debug that
>> configuration. I'd like to do the same with the rest of the output
>> as well. There's so much out of things like MIME headers and
>> response bodies that looking for other information can be a bit
>> tedious. I'd like to clean that up unless someone's terribly
>> attached to how things are now. Any objections?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>