At 06:51 PM 1/5/2005, you wrote:
Thanks Ceki -
I was hoping this is where it would end up.
Does this use implicit actions?
Yes, it does.
I see that selfInitialize in o.a.l.joran.JoranConfigurator registers a
number of rules, but I don't see anything referring to
TriggeringEventEvaluators.
Conside
Thanks Ceki -
I was hoping this is where it would end up.
Does this use implicit actions? I see that selfInitialize in
o.a.l.joran.JoranConfigurator registers a number of rules, but I don't see
anything referring to
TriggeringEventEvaluators.
Scott
-Original Message-
From: [EMAIL
Hello Scott,
Since we have the possibility of configuring sub-components of
components, the expression parameter should be added to instances of
the appropriate TriggeringEventEvaluator. Once of the reasons behind
the development of Joran was to address the problem of configuring
sub-components of
On Tue, 14 Dec 2004, Ceki Gülc <[EMAIL PROTECTED]> wrote:
> The fact that a small typo affects 200 projects should tell you that
> something is wrong with Gump's current approach.
Absolutely agreed. We know we could do better, we just haven't had
the time/skills to change it yet.
> For example,
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.
On Wednesday 15 December 2004 02:41, Mark Womack wrote:
> If there are that many projects in there, all dependent on
> each other in a multitude of ways, it amazes me that Gump ever completes a
> nightly build of all the projects. I like Gump, I support it, but I am not
> going to take special ac
ecompile before submitting. And Jake had that
strange compile behavior recently too.
-Mark
-Original Message-
From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 14, 2004 7:48 AM
To: Log4J Developers List
Subject: Re: cvs commit: logging-log4j/src/java/org/a
At 04:48 PM 12/14/2004, Niclas Hedhman wrote:
On Tuesday 14 December 2004 22:57, Ceki Gülcü wrote:
My sincerest apologies. Of course, Log4J are entitled to "fuck up" from time
to time. That is not something I want to undermine, and if it came across
like that, then I am truly sorry.
Niclas, there i
Niclas et al.,
IMHO, the kind of urgent pleas as the one by Niclas (quoted below) are
quite inappropriate. We, the log4j developers, have the right to
occasionally fuck up like every one else. The fact that a small typo
affects 200 projects should tell you that something is wrong with
On Tuesday 14 December 2004 00:22, [EMAIL PROTECTED] wrote:
> Index: SMTPAppender.java
> ===
> /home/cvs/logging-log4j/src/java/org/apache/log4j/net/SMTPAppender.java,v
> retrieving revision 1.35
> retrieving revision 1.36
> -
On Tuesday 14 December 2004 14:20, Mark Womack wrote:
> Not sure how you want to resolve this.
May I suggest a revert of the change first, and then think about how it should
be done?? :o) (only 200 projects are affected...)
Cheers
Niclas
--
+--//---+
/ http://www.dp
Yoav,
This change does not compile. The ErrorHandler interface does not support
error(String,Exception). Not sure how you want to resolve this. I took a
quick look, and there are methods that take an Exception, but they also
require other parameters, like an error code.
[javac]
D:\develo
On Tuesday 14 December 2004 22:57, Ceki Gülcü wrote:
> When a totally silly problem attains such cataclysmic proportions, it
> puts us (log4j developers) under unnecessary and useless
> pressure.
My sincerest apologies. Of course, Log4J are entitled to "fuck up" from time
to tim
13 matches
Mail list logo
