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] Updated: (JCR-1751) Update slf4j
Date Tue, 23 Sep 2008 16:17:44 GMT

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

Jukka Zitting updated JCR-1751:
-------------------------------

      Component/s: maven
    Fix Version/s: 1.5
         Assignee: Jukka Zitting

I'm wondering if a better solution would be *not* to use jcl-over-slf4j at all in Jackrabbit,
i.e. leave it up to the client application to exclude the transitive commons-logging dependency
with jcl-over-slf4j they want.

> Update slf4j
> ------------
>
>                 Key: JCR-1751
>                 URL: https://issues.apache.org/jira/browse/JCR-1751
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: maven
>            Reporter: Stephane Landelle
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.5
>
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
>
> Please update slf4j from 1.3.0 to 1.5.2.
> jcl104-over-slf4j has been renamed as jcl-over-slf4j, so if one uses a recent version,
he has to exclude jcl104-over-slf4j for every jackrabbit dependency, which is quite a pain...
> No impact observed.
> Best regards,
> Stephane Landelle

-- 
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