[ https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847504#comment-13847504 ]
Robert Munteanu commented on SLING-3049: ---------------------------------------- Thanks! I've also updated the bundle list to refer to the latest snapshot in http://svn.apache.org/r1550733 . The problem should be gone in the next build. > Make Logback Stacktrace Packaging data support OSGi aware > --------------------------------------------------------- > > Key: SLING-3049 > URL: https://issues.apache.org/jira/browse/SLING-3049 > Project: Sling > Issue Type: Improvement > Components: Commons > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Labels: logback > Fix For: Commons Log 4.0.0 > > Attachments: SLING-3049.patch, > buildbot-exceptions-while-stopping-jetty.txt > > > Logback provides a useful feature where it dumps the Class packaging Data > along with the stacktrace [1]. This provides a quick view of the location > from where classes in a given stacktrace are coming. Its default logic does > not work properly in OSGi env. Hence it would be useful to patch its logic to > become OSGi aware > [1] http://logback.qos.ch/reasonsToSwitch.html#packagingData -- This message was sent by Atlassian JIRA (v6.1.4#6159)