[
https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852788#action_12852788
]
Sean Owen commented on MAHOUT-361:
----------------------------------
Yah in theory it's their project that should depend on an slf4j implementation,
not Mahout. But that represents a gotcha, and, if you are right that their
dependency will override (does it? because then two bindings are on the
classpath? or if properly overridden, their "job" jars won't have our
dependency?) then it's good. I like.
> 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.
