gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam R. B. Jack" <aj...@apache.org>
Subject Fw: [GUMP@brutus]: jakarta-commons/commons-logging failed
Date Wed, 12 May 2004 13:51:24 GMT
What say this takes a while to resolve? Could we look for a recent tag on
log4j, create a log4j module (to tag) and a separate log4j-1.3 module (CVS
HEAD) and buy some time?

Clearly we ought wait a little while to see what transpires, but since this
seems a legitimate API change (2 years deprecated) and I'm curious about how
we work with such situations. This solution seems temporarily promising,
although the clean-up work might be more.

regards,

Adam
----- Original Message ----- 
From: "Ceki Gülcü" <ceki@qos.ch>
To: <commons-dev@jakarta.apache.org>
Cc: <log4j-dev@logging.apache.org>
Sent: Wednesday, May 12, 2004 2:26 AM
Subject: RE: [GUMP@brutus]: jakarta-commons/commons-logging failed


>
> 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 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, message, t );
> >
> >need to be changed to
> >
> >   getLogger().log(FQCN, Logger.FATAL, message, t );
> >
> >There 5 or 6 such lines in commons-logging. Note that the resulting
> >commons-logging code will run on both log4j 1.2.x and 1.3
> >
> >I hope this helps,
> >
> >At 12:56 AM 5/12/2004, Paul Smith wrote:
> >
> >>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 Smith
> >
> >--
> >Ceki Gülcü
> >
> >      For log4j documentation consider "The complete log4j manual"
> >      ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
> -- 
> Ceki Gülcü
>
>       For log4j documentation consider "The complete log4j manual"
>       ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org


Mime
View raw message