[slf4j-user] Release of SLF4J 1.3.0

[Ceki Gülcü]

I just committed a fix to this problem (see revision 1437). The 
ch.qos.logback.classic.Logger now implements 
org.slf4j.spi.LocationAwareLogger interface which should fix the problem as 
described by Franck.

Franck, would you care to check whether this fixes the problem for you?


At 02:44 PM 3/15/2007, Sebastien Pennec wrote:
>Hello Franck,
>
>The bug 23 has been tested and should be fixed in SLF4J. However, I fear 
>that what
>you are experiencing might be a bug in logback.
>
>We are going to check it out and correct it in our next release.
>
>As far as I know, there is nothing that you can do to correct the output 
>before we
>fix the bug in logback.
>
>Thanks for the report,
>
>Sébastien
>
>
>Franck Routier wrote:
> > Hi,
> >
> > I have upgraded to slf4j 1.3.0, but I still can see bug 23 behaviour...
> > (I think)
> >
> > Here is an example output :
> >
> > 158699 [Shutdown] INFO   org.apache.commons.logging.impl.SLF4JLog -
> > Shutting down Quartz Scheduler
> >
> > I have some libs using commons.logging, so I have
> > jcl104-over-slf4j-1.3.0.jar --> slf4j 1.3.0 --> logback 0.9.2
> >
> > My appender looks like this :
> >
> > <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
> >         <layout class="ch.qos.logback.classic.PatternLayout">
> >              <param name="pattern"
> >                   value="%-4relative [%thread] %-5level %marker %class -
> > %msg%n" />
> >         </layout>
> >     </appender>
> >
> > Is there anything I should change in the conf files to get the correct
> > output ?
> >
> > Franck
> >
> >
> >
> > Ceki Gülcü a écrit :
> >> February 25th, 2007 - Release of SLF4J 1.3.0
> >>
> >> This release consists of rearrangement of classes among projects. More
> >> specifically, the org.slf4j.LoggerFactory class is now packaged within
> >> the slf4j-api.jar file instead of the various slf4j bindings. It
> >> follows that client code needs to depend on only slf4j-api in order to
> >> compile, while the various slf4j bindings are only needed as runtime
> >> dependencies. See also the Maven2-related FAQ entry:
> >>
> >>    http://www.slf4j.org/faq.html#maven2
> >>
> >> Bug number 23 has been fixed, at the cost of minor and backward
> >> compatible changes. In other words, jcl104-over-slf4j now preserves
> >> caller location information.
> >>
> >> It is now possible to obtain the root logger of the underlying logging
> >> implementation by requesting a logger named "ROOT". This feature was
> >> requested by Sebastien Davids in bug report 35.
> >>
> >> You can download SLF4J, including full source code, class files and
> >> documentation on our download page, shown below.
> >>
> >>      http://www.slf4j.org/download.html
> >>
> >> You can receive SLF4J related announcements by subscribing to the
> >> SLF4J announce mailing list. To subscribe to SLF4J-announce list,
> >> please visit the following URL.
> >>
> >>      http://www.slf4j.org/mailman/listinfo/announce
> >>
> >> Enjoy,
> >>
> >>
> >>
> >>
> >
> >
> > _______________________________________________
> > user mailing list
> > user at slf4j.org
> > http://www.slf4j.org/mailman/listinfo/user
> >
>
>--
>Sébastien Pennec
>sebastien at qos.ch
>
>Logback: The reliable, generic, fast and flexible logging framework for Java.
>http://logback.qos.ch/
>_______________________________________________
>user mailing list
>user at slf4j.org
>http://www.slf4j.org/mailman/listinfo/user

-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch