[
https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3049:
-----------------------------------
Attachment: buildbot-exceptions-while-stopping-jetty.txt
In both [the buildbot sling-trunk build
41|http://ci.apache.org/builders/sling-trunk/builds/41/steps/compile/logs/stdio]
and [jenkins sling-1.6 build
2057|https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/2057/consoleText]
I can see that when Jetty shuts down errors are thrown related to logback
logging.
I've attached [^buildbot-exceptions-while-stopping-jetty.txt] , which contains
these errors.
> 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)
