[
https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852842#action_12852842
]
Drew Farris commented on MAHOUT-361:
------------------------------------
Sorry, I probably wasn't being clear; I'm not proposing we switch to the jcl
(commons-logging) api. I think we should continue to use the slf4j api and
continue to use the slf4j-jcl adapter. I do not think we should switch to use
the jcl logging api.
So, it sounds like we are all in agreement, the only change that would need to
be made to the existing core pom would be to remove the test scope for the
slf4j-jcl adapter dependency. I'm unsure if there are issues with the other
poms. Not in the position to look at this moment.
> 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.
