[
https://issues.apache.org/jira/browse/JCR-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633796#action_12633796
]
Stephane Landelle commented on JCR-1751:
----------------------------------------
I agree, jackrabbit shouldn't in any way depend on jcl104-over-slf4j with a
compile scope.
Currently, only jackrabbit-webapp and jackrabbit-text-extractor depend on
jcl104-over-slf4j (both with compile scope).
Concerning jackrabbit-webapp, scope should be runtime, not compile as it is
now.
Concerning jackrabbit-text-extractor, I don't understand why it depends on
jcl104-over-slf4j in the first place. Should it be remove? Should scope be
changed to test?
Sincerely,
Stephane Landelle
2008/9/23 Jukka Zitting (JIRA) <[EMAIL PROTECTED]>
> 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.
