The Cactus builds still fail in the same manner when run with log4j 1.2, so I assume that their breakage was just coincidental with our breaking hivemind. With my recent changes, there is no need to change Hivemind.

It does not appear that the internal logging suppression was totally effective. The gump output for hivemind (http://brutus.apache.org/gump/public/jakarta-hivemind/jakarta- hivemind/gump_work/build_jakarta-hivemind_jakarta-hivemind.html) still shows a lot of "log4j:INFO Creating new logger" messages.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to