[jira] [Reopened] (SLING-3049) Make Logback Stacktrace Packaging data support OSGi aware

2017-10-28 Thread Chetan Mehrotra (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra reopened SLING-3049:


> 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
> 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)


[jira] [Reopened] (SLING-3049) Make Logback Stacktrace Packaging data support OSGi aware

2013-11-20 Thread Chetan Mehrotra (JIRA)

 [ 
https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra reopened SLING-3049:



As per SLING-3252 we need to revert the changes done and wait for next release 
of Logback jar

 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


 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#6144)