You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/11/20 14:10:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Chetan Mehrotra resolved SLING-3049.
------------------------------------
Resolution: Fixed
Fix Version/s: Commons Log 5.0.4
Merged the changes to master. Feature is disabled by default and can be enabled by setting config/framework property "org.apache.sling.commons.log.packagingDataEnabled" to true
> 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 5.0.4
>
> 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.4.14#64029)