You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2010/05/28 18:27:40 UTC
[jira] Commented: (MAHOUT-361) SLF4J dependency structure leads to
unpleasant surproses
[ https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873039#action_12873039 ]
Hudson commented on MAHOUT-361:
-------------------------------
Integrated in Mahout-Quality #32 (See [http://hudson.zones.apache.org/hudson/job/Mahout-Quality/32/])
MAHOUT-361 -- just update to slf4j 1.6
> 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: Sean Owen
> Fix For: 0.4
>
> Attachments: MAHOUT-361.patch
>
>
> 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.