[
https://issues.apache.org/jira/browse/MAHOUT-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234409#comment-16234409
]
Trevor Grant commented on MAHOUT-2020:
--------------------------------------
Ok-
(1) the Multi-Artifact biuld hasn't merged yet.
(2) Scala 2.11 absolutely builds, and builds scala 2.11
`mvn clean install -Pscala-2.11`
That isn't to say sbt doesn't know what its doing. I never tested with that
build tool. But you can build a scala-2.11 app and submit to SPark 2.1 cluster
with scala 2.11 with no prob, and I can verify it is picking up scala 2.11,
because if you build with scala 2.10 and submit that to a flink-2.11 cluster or
vice verse it all goes haywire.
Will test your issues/try to learn sbt to reproduce.
> 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)
