GitHub user reminia opened a pull request:

    https://github.com/apache/zeppelin/pull/2470

    [ZEPPELIN-2648] Fix spark module build problem with scala-2.10 profile

    *  remove scala version in spark2 profile , we should compose scala profile 
and spark profile to address scala and spark version
    *  address scalaVersion evidently in maven-scala-plugin
    
    ### What is this PR for?
    details by ZEPPELIN-2648
    
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    None
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-2648
    
    
    ### How should this be tested?
    execute below command and check whether the zeppelin-spark artifact is 
build based on specified scala  and spark version.
     
    mvn clean package -Pscala-2.10 -Pspark-2.1
    
    mvn clean package -Pscala-2.11 -Pspark-2.1
    
    ### Screenshots (if appropriate)
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


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

    $ git pull https://github.com/reminia/zeppelin zeppelin-2648

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

    https://github.com/apache/zeppelin/pull/2470.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 #2470
    
----
commit fb57494b33a53713653c612e86bf5dece86daa97
Author: lichenyang <licheny...@cmss.chinamobile.com>
Date:   2017-07-07T01:46:57Z

    [ZEPPELIN-2648] Fix spark module build problem with scala-2.10 profile
    
    *  remove scala version in spark2 profile , we should compose scala profile 
and spark profile to address scala and spark version
    *  address scalaVersion evidently in maven-scala-plugin

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to