[
https://issues.apache.org/jira/browse/SLING-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847427#comment-13847427
]
Chetan Mehrotra commented on SLING-3049:
----------------------------------------
With [1550694|http://svn.apache.org/r1550694] I have disabled support for
PackagingDataCalculator all together. The way it computes PackagingData would
cause issue in OSGi environment. Also the support we had required a locally
modified file of Logback and which with its EPL licences would anyway have to
be removed.
So with this disabled we should not see this issue. Later if Logback does
include the fix for LOGBACK-899 users can still enable it as suggested in
SLING-3257. Leaving it open for now, once it is confirmed that above issue is
not seen anymore would close the bug as WontFix
> 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)
