You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by James Strachan <ja...@gmail.com> on 2007/06/12 17:40:13 UTC
lets not use System.out in unit tests!
It makes for messy output when running maven builds. Lets stick to
commons-logging please.
If folks find themselves wanting to turn on System.out type logging in
IDEs, we could add some base classes in test base classes to wrap the
clogging/System.out stuff (so System.out is only enabled inside an IDE
with some system property or something)
--
James
-------
http://macstrac.blogspot.com/
Re: lets not use System.out in unit tests!
Posted by James Strachan <ja...@gmail.com>.
On 6/13/07, Rob Davies <ra...@gmail.com> wrote:
> I wonder if putting in the option to support System.out in a base
> test class first rather than removing all the System.out calls first
> would have been a better option?
Thanks for volunteering! :)
--
James
-------
http://macstrac.blogspot.com/
Re: lets not use System.out in unit tests!
Posted by Rob Davies <ra...@gmail.com>.
I wonder if putting in the option to support System.out in a base
test class first rather than removing all the System.out calls first
would have been a better option?
On Jun 12, 2007, at 4:40 PM, James Strachan wrote:
> It makes for messy output when running maven builds. Lets stick to
> commons-logging please.
>
> If folks find themselves wanting to turn on System.out type logging in
> IDEs, we could add some base classes in test base classes to wrap the
> clogging/System.out stuff (so System.out is only enabled inside an IDE
> with some system property or something)
>
> --
> James
> -------
> http://macstrac.blogspot.com/