On Feb 22, 2005, at 6:25 AM, Knut Wannheden wrote:
Hi,
For the last few GUMP builds of Jakarta HiveMind we got build failure
notifications. We are building against the latest build of log4j and get the
following error message:
[junit] log4j:INFO Returning existing logger [org.apache.hivemind] in
repository [default].
[junit] 22226 [main] ERROR org.apache.hivemind.test.StoreAppender -
Attempted to log with inactive appender named [null].
[junit] log4j:INFO Returning existing logger [org.apache.hivemind] in
repository [default].
It looks like it's a recent change in the Appender interface (new methods
activate() and isActive()) which is causing this problem for us as we use a
custom Appender implementation to intercept logging events.
Do you suggest we instruct GUMP to build HiveMind against a 1.2.x version of
log4j?
I agree with your analysis of the problem. If you need to restore Gump immediately, backing up to log4j 1.2 would be the most expedient approach. I don't think the recent changes got the amount of discussion that was warranted for a breaking change and we might be able to restore compatibility in short order. So if you are willing to be broken for a few days, maybe we can eliminate the need for you to do anything.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
