Curt and Ceki,
Curt Arnold apache.org> writes:
>
> Actually, looking at the Gump messages in the Hivemind mailing list
> suggest that the problem was all along the lack of an activateOptions
> call before adding an appender and was never the addition of
> isClosed(), isActive() and activa
Curt Arnold apache.org> writes:
> logging-log4j-tests was successful.
>
> hivemind
> (http://brutus.apache.org/gump/public/jakarta-hivemind/jakarta-
> hivemind/gump_work/build_jakarta-hivemind_jakarta-hivemind.txt)
> appeared to fail due the following check in AppenderSkeleton:
>
>publ
Curt,
Curt Arnold apache.org> writes:
> 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 cha
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] 6 [ma
