[
https://issues.apache.org/jira/browse/MAHOUT-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved MAHOUT-820.
------------------------------
Resolution: Fixed
Fix Version/s: 0.6
Assignee: Sean Owen
I agree. I see we need to explicitly specify this everywhere. Done.
> Dependency on sjl4j-jcl should not have compile scope
> -----------------------------------------------------
>
> Key: MAHOUT-820
> URL: https://issues.apache.org/jira/browse/MAHOUT-820
> Project: Mahout
> Issue Type: Bug
> Components: build
> Affects Versions: 0.6
> Reporter: Aaron Kaplan
> Assignee: Sean Owen
> Priority: Minor
> Fix For: 0.6
>
>
> The top-level pom.xml and integration/pom.xml specify a dependency on
> slf4j-jcl with default (compile) scope. The point of slf4j is to allow
> libraries to work with any underlying logging system, leaving the choice up
> to the application programmer. If my application uses jcl-over-slf4j, and
> also uses your library which uses slf4j-jcl, initialization fails because
> there's a logging loop.
> core/pom.xml and math/pom.xml specify slf4j-jcl with test scope only. That's
> fine, because dependencies with test scope aren't propagated to dependents.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
