In M1 there was a way to say swallow ouput. I can not find a
reference to it. But trying..
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
I'm not sure how they were quiet before m2 with code like above
in setUp().
--jason
On Aug 28, 2006, at 4:29 PM, Jason Dillon
Ya, I'm not sure that surefire has support for that :-(
--jason
On Aug 31, 2006, at 6:35 AM, anita kulshreshtha wrote:
In M1 there was a way to say swallow ouput. I can not find a
reference to it. But trying..
Thanks
Anita
--- Jason Dillon [EMAIL PROTECTED] wrote:
I'm not sure how
Um... looks like a few of these tests are explicitly enabling DEBUG
and installing a ConsoleAppender...
Logger.getRootLogger().addAppender(new ConsoleAppender(new
PatternLayout(%p [%t] %m %n)));
Logger.getRootLogger().setLevel(Level.DEBUG);
I'm not sure how they were quiet before
This is fixed now... though it still spits out a few ERROR logs,
which I am hoping are expected from the test...
--jason
On Aug 30, 2006, at 3:49 PM, Jason Dillon wrote:
Um... looks like a few of these tests are explicitly enabling DEBUG
and installing a ConsoleAppender...
Looks like there is more going on which is causing tests to use some
additional configuration for tests...
Specifically, looks like something else is installing a
ConsoleAppender... as if I comment out the CONSOLE definition from
logging-config, then I still get console output.
I'm also
You should be able to turn on debugging, add a break point in the
logging code and see which test is causing the problem.
-dain
On Aug 30, 2006, at 4:31 PM, Jason Dillon wrote:
Looks like there is more going on which is causing tests to use
some additional configuration for tests...
I think this is related to the custom log4j bits on geronimo-kernel,
which most modules depend on. Modules that do not depend on geronimo-
kernel, like geronimo-util and geronimo-activation behave as I would
expect.
I'm gonna dig into it more, and will probably add a custom sys prop
to
Okay, I think I've found it... BootstrapLog4jLog and
BootstrapJdk1.4Log both have static blocks that install logging
configuration programatically.
I'm going to add a new method to GeronimoLogging, which will check if
this behavior is enabled or not:
/**
* Check if the Geronimo
Looks like logging-config is not getting picked up as I had
expected... going to need to write a custom goal that will install the
logging configuration into target/test-classes so that it gets pick up
first.
--jason
On 8/28/06, Jason Dillon [EMAIL PROTECTED] wrote:
Thats odd, because the
These tests make way... way to much noise.
Anyone know how to make them shut up?
--jason
Not me. They were quiet before the m2 change but it looks like
logging got turned up.
-dain
On Aug 28, 2006, at 2:26 AM, Jason Dillon wrote:
These tests make way... way to much noise.
Anyone know how to make them shut up?
--jason
Thats odd, because the default logging config is set to only allow
WARN and ERROR to go to console, not DEBUG.
Do these tests need to:
GeronimoLogging.initialize(GeronimoLogging.INFO);
Or something?
--jason
On Aug 28, 2006, at 10:14 AM, Dain Sundstrom wrote:
Not me. They were quiet
12 matches
Mail list logo
