You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2010/12/20 15:55:03 UTC

[jira] Closed: (SLING-1739) Update Commons Log exported SLF4J version

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

Carsten Ziegeler closed SLING-1739.
-----------------------------------


> Update Commons Log exported SLF4J version
> -----------------------------------------
>
>                 Key: SLING-1739
>                 URL: https://issues.apache.org/jira/browse/SLING-1739
>             Project: Sling
>          Issue Type: Improvement
>          Components: Commons
>    Affects Versions: Commons Log 2.0.6
>            Reporter: Jason Rose
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: Commons Log 2.1.0
>
>         Attachments: commons-log.patch
>
>
> Commons Log is currently exporting version 1.5.2 of SLF4j.  This is a very old version of the library.  I'm currently using Commons Logging as a replacement for PAX Logging because of classloading issues with PAX in JBoss, and I needed to make a couple changes to facilitate that.
> Updating the dependency and exported versions of SLF4j fixes most of the issues I have with trying to exclusively use Commons Log.  In addition to updating the version, I've moved the spi and helpers packages into the exported packages instead of private packages.  This makes it mirror PAX more closely and handles all the logging requirements of 3rd party bundles in my application.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.