Log4j 1.2alpha is perfectly backward compatible with 1.1.3. It's not maybe or perhaps. Please provide exact details about the nature of the problem. Thank you, Ceki
At 11:40 08.02.2002 -0500, Glen Daniels wrote: >Hi all! > >I think this is a result of the change to make Category extend >Logger. All of our code uses Category, and so using code compiled with >log4j 1.2 with log4j 1.1.3 causes some problem with Logger not being >found. Sorry I can't be more detailed myself. Are you guys aware of any >problems like this? > >--Glen > > > -----Original Message----- > > From: Tom Jordahl [mailto:[EMAIL PROTECTED]] > > Sent: Friday, February 08, 2002 11:36 AM > > To: '[EMAIL PROTECTED]' > > Cc: '[EMAIL PROTECTED]' > > Subject: RE: Interop with Log4j > > > > > > Tom Jordahl wrote: > > > The latest log4j from CVS has made a incompatible change > > from the previous > > > release version. > > > > Sam Ruby wrote: > > > Have you communicated this to the log4j development team? > > Such changes > > > would eventually impact Axis users... I can tell you that > > the log4j team > > > takes backwards compatibility very seriously and > > agressively address any > > > issues brought to their attention. > > > > I have not in fact communicated with the log4j team. Hi guys! > > > > Here is what I know: If you try to use the nightly build > > axis.jar with the log4j.jar checked in to our CVS tree, it > > will fail due to a missing log4j class. I apologize for not > > having the class name handy. > > > > -- > > Tom Jordahl > > Macromedia > > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Ceki Gülcü
