Discussion:
Test : preventing expected stack trace in the console
Olivier Catteau
2006-11-11 21:34:32 UTC
Permalink
Hi,

I have a lot of unit tests in my app. When the tests runs, I see numerous
expected stack traces logged in the console and at the end I get a normal
Build Successful (but the first impression is that it failed).
I would like that these expected stack traces don't appear in the console
(in maven1, these traces wasn't logged). Is it possible ?

Thanks.
Olivier
Wim Deblauwe
2006-11-12 09:36:03 UTC
Permalink
I already posted the same question a few days ago, but no answer yet. Maybe
we should file a bug on this? It is annoying when converting to Maven 2,you
don't get the same functionality.

regards,

Wim
Post by Olivier Catteau
Hi,
I have a lot of unit tests in my app. When the tests runs, I see numerous
expected stack traces logged in the console and at the end I get a normal
Build Successful (but the first impression is that it failed).
I would like that these expected stack traces don't appear in the console
(in maven1, these traces wasn't logged). Is it possible ?
Thanks.
Olivier
dawn.angelito
2006-11-13 05:46:16 UTC
Permalink
Hi Olivier and Wim,

Try using the "--quiet" option. It will change the logging level to ERROR.

Hope this helps.

Dawn
Post by Wim Deblauwe
I already posted the same question a few days ago, but no answer yet. Maybe
we should file a bug on this? It is annoying when converting to Maven 2,you
don't get the same functionality.
regards,
Wim
Post by Olivier Catteau
Hi,
I have a lot of unit tests in my app. When the tests runs, I see numerous
expected stack traces logged in the console and at the end I get a normal
Build Successful (but the first impression is that it failed).
I would like that these expected stack traces don't appear in the console
(in maven1, these traces wasn't logged). Is it possible ?
Thanks.
Olivier
--
View this message in context: http://www.nabble.com/Test-%3A-preventing-expected-stack-trace-in-the-console-tf2614478s177.html#a7311768
Sent from the Maven - Users mailing list archive at Nabble.com.
Mirko Nasato
2006-11-13 16:23:37 UTC
Permalink
Same problem here.
Post by dawn.angelito
Try using the "--quiet" option. It will change the logging level to ERROR.
The "--quiet" option doesn't seem to exist in Maven 2.0.4

$ mvn --quiet test
Unable to parse command line options: Unrecognized option: --quiet
...

I've also tried the "redirectOutputToFile" option but it doesn't make a
difference.**

Other ideas?

Thanks

Mirko
Post by dawn.angelito
Post by Wim Deblauwe
I already posted the same question a few days ago, but no answer yet. Maybe
we should file a bug on this? It is annoying when converting to Maven 2,you
don't get the same functionality.
regards,
Wim
Post by Olivier Catteau
Hi,
I have a lot of unit tests in my app. When the tests runs, I see numerous
expected stack traces logged in the console and at the end I get a normal
Build Successful (but the first impression is that it failed).
I would like that these expected stack traces don't appear in the console
(in maven1, these traces wasn't logged). Is it possible ?
Thanks.
Olivier
Loading...