You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2010/04/03 01:29:27 UTC

[jira] Updated: (MAHOUT-361) SLF4J dependency structure leads to unpleasant surproses

     [ https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated MAHOUT-361:
-----------------------------

    Attachment: MAHOUT-361.patch

This is what it looks like to remove logging from math and collections. It's something to consider separately from the main conversation. Since the module in question was math/collections, maybe this is a helpful step anyway. Fewer dependencies in core libraries are better. But does this lose anything valuable? I sense this is left over from Colt?

> 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
>         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.