[
https://issues.apache.org/jira/browse/MAHOUT-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852792#action_12852792
]
Drew Farris commented on MAHOUT-361:
------------------------------------
I've run into this too as a result of having the slf4j implementation in test
scope.
Can we consider continuing to use the jcl adapter instead of jdk14?
A large number of Mahout's dependenices already use jcl for their logging.
Using this adapter changing the logging behavior for mahout (and its
dependencies) becomes as simple as adding log4j (or not) to the jars (as
opposed to switching the jcl version of slf4j >and< adding log4j). Admittedly
this a minor difference, but one less thing to change. The default behavior is
to use jdk14 anyway.
I propose that we remove the test scope from the slf4j-jcl adapter dependency
and let it default to the compile scope. Benson, this should solve the issue
too, correct?
> 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.
