At 07:41 PM 12/14/2004, Mark Womack wrote:
The fact that 200 projects were affected in Gump is a Gump problem, not a
log4j problem.
Gump is reportedly being improved to avoid the recent observed massive
breakdown. However, when 200 projects start blaming log4j, then things
become much less obvious.
The point I am trying to make is that when projects like log4j, with
many dependents, have compilation issues, Gump currently raises way
too many alarms. Again, this is being reportedly worked upon.
If you go back and read Niclas' first message, you should notice the
urgent tone, where, as I am trying to explain, there should have been
no urgency.
I'm more concerned that there might be something up with the main log4j
build script. Yoav did a recompile before submitting. And Jake had that
strange compile behavior recently too.
Are you going to check?
-Mark
--
Ceki Gülcü
The complete log4j manual:
https://www.qos.ch/shop/products/log4j/log4j-Manual.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
