You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jason Moore (JIRA)" <ji...@apache.org> on 2018/11/13 00:49:00 UTC
[jira] [Commented] (SPARK-26027) Unable to build Spark for Scala
2.12 with Maven script provided
[ https://issues.apache.org/jira/browse/SPARK-26027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684567#comment-16684567 ]
Jason Moore commented on SPARK-26027:
-------------------------------------
Actually, the fact that scala-library 2.11.12 is downloaded to launch the zinc server turned out to be a red herring and my issue was not properly setting the profile to scala-2.12. I'm not sure of the repercussion of having the zinc server started by ./build/mvn having 2.11.12 though (see [https://github.com/apache/spark/blob/master/build/mvn#L155|https://github.com/apache/spark/blob/master/build/mvn#L155).]) so maybe someone with a more intimate knowledge of it can comment.
> Unable to build Spark for Scala 2.12 with Maven script provided
> ---------------------------------------------------------------
>
> Key: SPARK-26027
> URL: https://issues.apache.org/jira/browse/SPARK-26027
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.4.0
> Reporter: Jason Moore
> Priority: Minor
>
> In ./build/mvn, <scala.version> from pom.xml is used to determine which Scala library to fetch but it doesn't seem to use the value under the scala-2.12 profile even if that is set.
> The result is that the maven build still uses scala-library 2.11.12 and compilation fails.
> Am I missing a step? (I do run ./dev/change-scala-version.sh 2.12 but I think that only updates scala.binary.version)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org