We have analyzed the Gump breakage of Hivemind and have been able to
suppress the problem. However it didn't clean up the problem with the
Cactus Gump runs. I made a half-hearted effort to set up a build
environment for Cactus but abandoned it. It would be really helpful if
someone could check that log4j was responsible for the breakage but
running any of the affected tests with both a pre-17 Feb log4j and a
post-17 Feb log4j (you could just use the ones from Gump). If so, it
would be extremely lovely if you can try to figure out the nature of
the change in behavior that caused Cactus to break.
I may try to do some Gump shenanigans to have it help.
On Feb 22, 2005, at 11:55 PM, Curt Arnold wrote:
There have been recent changes to log4j that have broken the Gump
build of jakarta-hivemind. The start of yourt Gump build failures
coincide with the log4j changes and the breaking of hivemind. Do you
know if our recent changes were the cause of your Gump failures too?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
