[
https://issues.apache.org/jira/browse/SLING-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878555#comment-13878555
]
Chetan Mehrotra commented on SLING-3252:
----------------------------------------
bq. Assuming the current logback trunk was released, would it allow use to
remove the logback classes that we currently include?
Yup.
* [LOGBACK-384|http://jira.qos.ch/browse/LOGBACK-384] is critical and is fixed.
* [LOGBACK-899|http://jira.qos.ch/browse/LOGBACK-899] is kind of good to have
feature and optional. Further it causes issue in OSGi env as explained in
[SLING-3049|https://issues.apache.org/jira/browse/SLING-3049?focusedCommentId=13847427]
> Remove checked in Logback related classes before 4.x release
> ------------------------------------------------------------
>
> Key: SLING-3252
> URL: https://issues.apache.org/jira/browse/SLING-3252
> Project: Sling
> Issue Type: Task
> Components: Commons
> Affects Versions: Commons Log 4.0.0
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Blocker
> Fix For: Commons Log 4.0.0
>
>
> Currently the Common Log bundle has checked in 2 Logback classes as a fix for
> SLING-3037 and SLING-3049. These classes are under EPL and cannot be part of
> released bundle
> See http://sling.markmail.org/thread/ilixl3ebdd3hxxts
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
