jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2584) Switch from log4j to Logback
Date Wed, 07 Apr 2010 17:08:34 GMT

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

Jukka Zitting resolved JCR-2584.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.1.0)
                   2.2.0
         Assignee: Jukka Zitting

I switched the dependency in Jackrabbit trunk. This may be a bit too late for 2.1, so I won't
merge the changes to the branch. Instead targeting Jackrabbit 2.2.

> Switch from log4j to Logback
> ----------------------------
>
>                 Key: JCR-2584
>                 URL: https://issues.apache.org/jira/browse/JCR-2584
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jca, jackrabbit-standalone, jackrabbit-webapp
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.2.0
>
>
> Logback (http://logback.qos.ch/) is a native SLF4J implementation and is in many ways
superior to log4j (see http://logback.qos.ch/reasonsToSwitch.html). Most notably it includes
package version information in logged stack traces (http://logback.qos.ch/reasonsToSwitch.html#packagingData),
which can be really useful in many cases.

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


Mime
View raw message