[
https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852793#action_12852793
]
Benson Margulies commented on MAHOUT-361:
-----------------------------------------
It's a little worse than 'override'. They must write a Maven 'exclude' clause
into their dependency on Mahout, and then write a dependency for the back-end
they want.
This is perhaps why some people are shy of using SLF4J as their direct logging
API.
As per Drew, we could just make calls to JCL, and anyone who wants SLF4J
(including us in tests or utilities) can use their bridge.
Actually, I meant to write jcl, not jdk14, so that proposal is fine with me.
> SLF4J dependency structure leads to unpleasant surproses
> --------------------------------------------------------
>
> Key: MAHOUT-361
> URL: https://issues.apache.org/jira/browse/MAHOUT-361
> Project: Mahout
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 0.3
> Reporter: Benson Margulies
> Assignee: Benson Margulies
>
> Our poms declare a dependency on the slf4j core, but not on any of the
> implementation modules. Thus, if an unsuspecting user adds a dependency on
> our stuff, and runs, they get a exception from slf4j complaining that there's
> no implementation. I claim that it would be more better to declare a
> dependency on the JDK14 module, and those users who really care about using
> something else can exclude it and include their own.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
