I'm no expert on when to [or not to] cross post, but this looks like a good
topic for discussion in these two places at once.
regards
Adam
- Original Message -
From: "Mario Ivankovits" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Monday, May 17, 200
By the way, commons-logging developers could issue a maintenance
release of c-l now, months before log4j 1.3 is released.
At 09:55 AM 5/12/2004, Ceki Gülcü wrote:
Hello,
All hail gump. The use of Priority has been deprecated for over 2
years and it will be removed in log4j 1.3.
Fortunately, the r
At 12:59 AM 5/12/2004, Paul Smith wrote:
>
> Not sure if this will get sufficient attention without
> bringing it here, so
> doing so...
>
> Thanks in advance,
>
> regards
Ceki, looks like the recent change in Category changed from the old
Priority->Level, which will break existing installations wi
Hello,
All hail gump. The use of Priority has been deprecated for over 2
years and it will be removed in log4j 1.3.
Fortunately, the required changes are easy and are backward compatible.
Commons-logging code needs to be changed as follows.
Lines such as
getLogger().log(FQCN, Priority.FATAL, me
>
> Not sure if this will get sufficient attention without
> bringing it here, so
> doing so...
>
> Thanks in advance,
>
> regards
Ceki, looks like the recent change in Category changed from the old
Priority->Level, which will break existing installations with
commons-logging. Could we keep t
Hi All,
> Not sure if this will get sufficient attention without
> bringing it here, so
> doing so...
Yes, there has been a few changes under the hood in log4j recently. We'll
have to chat internally to see what we can do, and get back to you.
All hail gump for picking it up.
cheers,
Paul
