the problem is not in the stackTrace - it's general to all log levels when you want to log info/warn/error and to show the line number/ method that was fire this log
On Wed, May 8, 2013 at 1:17 PM, ceki <[email protected]> wrote: > > BTW, the output generated by following one-liner would be sufficient: > > new Exception("test").**printStackTrace(); > > > On 08.05.2013 11:10, ceki wrote: > >> Hi Menu, >> >> Thank you for your post. >> >> As you already know, a recent version of logback corrected a bug with >> caller extraction when running under groovy. Moreover, reports from >> the field indicate that the aforementioned bug fix solves the problem >> at hand. There must be something else going on. >> >> Could you please post a stack trace generated from a location where >> logback caller extraction does not work correctly? It can be any place >> where line number extraction fails. >> >> Best, >> >> On 08.05.2013 10:59, Meni Lubetkin wrote: >> >>> i'm using the logback plugin with grails 2.2.1 but it doesn't show the >>> method or the class name. i defined the pattern using the logback >>> reference but it not showing the line number or method name - it shows >>> -1 all the time >>> >>> You could also reference http://markmail.org/message/__** >>> hfxw2w5auaqdea7i <http://markmail.org/message/__hfxw2w5auaqdea7i> >>> <http://markmail.org/message/**hfxw2w5auaqdea7i<http://markmail.org/message/hfxw2w5auaqdea7i> >>> > >>> >>> the plugin is now updated to 10.0.12 version >>> >>> >> >> > > -- > Ceki > 65% of statistics are made up on the spot > ______________________________**_________________ > Logback-user mailing list > [email protected] > http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user> >
_______________________________________________ Logback-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/logback-user
