[
https://issues.apache.org/jira/browse/MAHOUT-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pat Ferrel updated MAHOUT-2020:
---
Description: 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. (was: The maven repo should build:
org/apache/mahout/mahout-spark-2.1/0.13.1-SNAPSHOT/mahout-spark-2.1_2.11-0.13.1-SNAPSHOT.jar
substitute Spark version for -2.1, so -1.6 etc.
The build.sbt `libraryDependencies` line then will be:
`"org.apache.mahout" %% "mahout-spark-2.1" % “0.13.1-SNAPSHOT`
This is parsed by sbt to yield the path of :
org/apache/mahout/mahout-spark-2.1/0.13.1-SNAPSHOT/mahout-spark-2.1_2.11-0.13.1-SNAPSHOT.jar
The outcome of `mvn clean install` currently is something like:
org/apache/mahout/mahout-spark/0.13.1-SNAPSHOT/mahout-spark-0.13.1-SNAPSHOT-spark_2.1.jar
This has no effect on the package structure, only artifact naming and maven
repo structure.)
> 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)
