[
https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877597#comment-13877597
]
Bertrand Delacretaz commented on SLING-3049:
--------------------------------------------
I had a look at http://jira.qos.ch/browse/LOGBACK-899 and in the discussion of
[~chetanm]'s pull request https://github.com/qos-ch/logback/pull/146 tony19
asks for the OSGi-specific part to be moved to the logback-extensions module.
I don't think this has been taken care of, and as a result the pull request has
now be closed.
[~chetanm], are you in touch with the logback folks about this?
> 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.5#6160)
