You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2011/01/04 16:09:45 UTC
[jira] Created: (JCR-2856) Upgrade to latest SLF4J and Logback
Upgrade to latest SLF4J and Logback
-----------------------------------
Key: JCR-2856
URL: https://issues.apache.org/jira/browse/JCR-2856
Project: Jackrabbit Content Repository
Issue Type: Improvement
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Priority: Minor
Fix For: 2.3.0
While fixing JCR-2836 I ran into LBCLASSIC-183 [1] that's fixed in a recent Logback release. To get this and other fixes we should upgrade Logback and SLF4J in Jackrabbit 2.3.
[1] http://jira.qos.ch/browse/LBCLASSIC-183
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2856) Upgrade to latest SLF4J and Logback
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2856.
--------------------------------
Resolution: Fixed
Upgraded to SLF4J 1.6.1 and Logback 0.9.27 in revision 1055075.
> Upgrade to latest SLF4J and Logback
> -----------------------------------
>
> Key: JCR-2856
> URL: https://issues.apache.org/jira/browse/JCR-2856
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.3.0
>
>
> While fixing JCR-2836 I ran into LBCLASSIC-183 [1] that's fixed in a recent Logback release. To get this and other fixes we should upgrade Logback and SLF4J in Jackrabbit 2.3.
> [1] http://jira.qos.ch/browse/LBCLASSIC-183
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.