[ 
https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852795#action_12852795
 ] 

Sean Owen commented on MAHOUT-361:
----------------------------------

Hoo boy, and we used to use JCL directly in 0.1. We come full circle. 

I still somehow favor sticking with SLF4J, mostly from inertia. But I dont' 
feel strongly.

But if we're dropping the meta-meta logger, why only drop down to meta-logger 
JCL? go all the way to JDK's logger. Hey, we already living in a situation 
where every major logger is used. Some of them have ways to redirect logging to 
other loggers. We can just use the most-primitive logger and let those who care 
redirect to JDK's logging?

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

Reply via email to