You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/02/03 22:22:00 UTC
[jira] [Commented] (SLING-3049) Make Logback Stacktrace Packaging
data support OSGi aware
[ https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351550#comment-16351550 ]
Robert Munteanu commented on SLING-3049:
----------------------------------------
[~chetanm] - is the 'Packaging Data' link from https://sling.apache.org/documentation/development/logging.html incorrect? It leads to http://www.slf4j.org/manual.html#mdc
> 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
> Priority: Major
> Labels: Sling-10-ReleaseNotes, logback
> Fix For: Commons Log 5.1.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
(v7.6.3#76005)