[
https://issues.apache.org/jira/browse/JCR-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting moved COMDEV-2 to JCR-2411:
-----------------------------------------
Workflow: no-reopen-closed, patch-avail (was: jira)
Key: JCR-2411 (was: COMDEV-2)
Project: Jackrabbit Content Repository (was: Community Development )
> 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
> Reporter: 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.
