GitHub user dongjoon-hyun opened a pull request:

    https://github.com/apache/spark/pull/23118

    [SPARK-26144][BUILD] `build/mvn` should detect `scala.version` based on 
`scala.binary.version`

    ## What changes were proposed in this pull request?
    
    Currently, `build/mvn` downloads and uses **Scala 2.12.7** in `Scala-2.11` 
Jenkins job. The root cause is `build/mvn` got the first match from `pom.xml` 
blindly.
    
    - 
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-2.7-ubuntu-scala-2.11/6/consoleFull
    ```
    exec: curl -s -L https://downloads.lightbend.com/zinc/0.3.15/zinc-0.3.15.tgz
    exec: curl -s -L 
https://downloads.lightbend.com/scala/2.12.7/scala-2.12.7.tgz
    exec: curl -s -L 
https://www.apache.org/dyn/closer.lua?action=download&filename=/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz
    ```
    
    ## How was this patch tested?
    
    Manual.
    ```
    $ build/mvn clean
    exec: curl --progress-bar -L 
https://downloads.lightbend.com/scala/2.12.7/scala-2.12.7.tgz
    ...
    $ dev/change-scala-version.sh 2.11
    $ build/mvn clean
    exec: curl --progress-bar -L 
https://downloads.lightbend.com/scala/2.11.12/scala-2.11.12.tgz
    ```

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dongjoon-hyun/spark SPARK-26144

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/23118.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #23118
    
----
commit f4f51af9fbc8b756ebd33e1be7e73cc62bfe081f
Author: Dongjoon Hyun <dongjoon@...>
Date:   2018-11-22T08:45:46Z

    [SPARK-26144][BUILD] `build/mvn` should detect `scala.version` based on 
`scala.binary.version`

----


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to