Carsten Ziegeler wrote:
So, please vote on the change.
and please vote if this is a change for 2.1.1 or 2.2.
+1 on 2.1.1.
Ugo
Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for the move already in bugzilla:
Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for the move already in bugzilla:
Vadim Gritsenko wrote:
Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for the move
Vadim Gritsenko wrote:
2.1.1, +1.
Or should it be 2.1.2? I thought you are going to release 2.1.1 Really
Soon Now? btw, what about 2.0.5?
:), yepp, we will see, we could rephrase it to 2.1.x then. I will not
release 2.1.1 without a fix for the event handling (commandmanager) bug.
It
Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for the move already in bugzilla:
On 29.Aug.2003 -- 02:20 PM, Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for
...and please vote if this is a change for 2.1.1 or 2.2.
+1 for 2.1.1
-Bertrand
On Fri, 29 Aug 2003, Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j,
I propose that we move from the deprecated LogKitManager
to the new LoggerManager. This will make using log4j much
easier (and I would implement that then next).
There is a patch for the move
