logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Wannheden <k...@apache.org>
Subject Re: HiveMind GUMP build failures
Date Tue, 22 Feb 2005 18:37:51 GMT

Curt Arnold <carnold <at> 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 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.

It is good to know that you are aware of the problem. We don't have any 
problem with the build being broken for a few days, so we will just wait for 
you to decide how you will proceed with this matter. I just wanted to check 
what the right course of action was to take.



To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message