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-2411) Replace commons-logging with jcl-over-slf4j in jackrabbit-webdav
Date Thu, 26 Nov 2009 16:56:40 GMT

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

Jukka Zitting updated JCR-2411:
-------------------------------

    Component/s: jackrabbit-webdav
                 jackrabbit-webapp
                 jackrabbit-jca
       Assignee: Jukka Zitting

Hmm, for some reason this bug got filed under COMDEV instead of JCR. Sorry for the confusion,
I've moved this to the correct place.

> Replace commons-logging with jcl-over-slf4j in jackrabbit-webdav
> ----------------------------------------------------------------
>
>                 Key: JCR-2411
>                 URL: https://issues.apache.org/jira/browse/JCR-2411
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jca, jackrabbit-webapp, jackrabbit-webdav
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>
> In JCR-1631 we moved the exclusion rule against the transitive commons-logging dependency
from commons-httpclient to higher level components like jackrabbit-jca and jackrabbit-webapp.
> However, I'm having some trouble with commons-logging showing up in other downstream
projects that depend directly on jackrabbit-webapp or jackrabbit-jcr-server. Thus I'd like
to revert the JCR-1631 solution and push the exclusion rule back to jackrabbit-webapp and
replace the commons-logging dependency with jcl-over-slf4j. Downstream projects that already
use commons-logging can still exclude the jcl-over-slf4j dependency.

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