[
https://issues.apache.org/jira/browse/SLING-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877598#comment-13877598
]
Bertrand Delacretaz commented on SLING-3252:
--------------------------------------------
Assuming the current logback trunk was released, would it allow use to remove
the logback classes that we currently include?
AFAIK those classes are workarounds for the following issues, but not sure if
that's the complete list:
http://jira.qos.ch/browse/LOGBACK-384 - looks like this will be included in
logback 1.1.0
http://jira.qos.ch/browse/LOGBACK-899 - not sure if this one is still needed,
[~chetanm] can you confirm?
> 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)
