[ https://issues.apache.org/jira/browse/MAHOUT-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190340#comment-16190340 ]
Pat Ferrel edited comment on MAHOUT-2020 at 11/1/17 1:23 AM: ------------------------------------------------------------- This may be a non-issue. Trevor said in email: {quote}The spark is included via maven classifier- the sbt line should be libraryDependencies += "org.apache.mahout" % "mahout-spark_2.11" % "0.13.1-SNAPSHOT" classifier "spark_2.1" {quote} This is a red herring, the real issue is scala 2.11 never builds correctly because poms end up with 2.10 as the scala.compat.version was (Author: pferrel): This may be a non-issue. Trevor said in email: {quote}The spark is included via maven classifier- the sbt line should be libraryDependencies += "org.apache.mahout" % "mahout-spark_2.11" % "0.13.1-SNAPSHOT" classifier "spark_2.1" {quote} > Maven repo structure malformed > ------------------------------ > > Key: MAHOUT-2020 > URL: https://issues.apache.org/jira/browse/MAHOUT-2020 > Project: Mahout > Issue Type: Bug > Components: build > Affects Versions: 0.13.1 > Environment: Creating a project from maven built Mahout using sbt. > Made critical since it seems to block using Mahout with sbt. At least I have > found no way to do it. > Reporter: Pat Ferrel > Assignee: Trevor Grant > Priority: Blocker > Fix For: 0.13.1 > > > The maven repo is built with scala 2.10 always in the parent pom's > {scala.compat.version} even when you only ask for Scala 2.11, this leads to > the 2.11 jars never being found. -- This message was sent by Atlassian JIRA (v6.4.14#64029)