Github user krystiannowak commented on the issue:

    https://github.com/apache/zeppelin/pull/1368
  
    @lresende It seems that when just executing
    ```
    mvn clean package -Pspark-1.6 -Phadoop-2.4 -Pyarn -Ppyspark -Pscala-2.11 
-DskipTests clean package
    ```
    it fails
    ```
    [INFO] 
------------------------------------------------------------------------
    [INFO] Reactor Summary:
    [INFO]
    [INFO] Zeppelin .......................................... SUCCESS [  8.430 
s]
    [INFO] Zeppelin: Interpreter ............................. SUCCESS [ 54.976 
s]
    [INFO] Zeppelin: Zengine ................................. SUCCESS [ 36.888 
s]
    [INFO] Zeppelin: Display system apis ..................... SUCCESS [01:09 
min]
    [INFO] Zeppelin: Spark dependencies ...................... SUCCESS [04:25 
min]
    [INFO] Zeppelin: Spark ................................... FAILURE [  5.676 
s]
    [INFO] Zeppelin: Markdown interpreter .................... SKIPPED
    [INFO] Zeppelin: Angular interpreter ..................... SKIPPED
    [INFO] Zeppelin: Shell interpreter ....................... SKIPPED
    [INFO] Zeppelin: Livy interpreter ........................ SKIPPED
    [INFO] Zeppelin: HBase interpreter ....................... SKIPPED
    [INFO] Zeppelin: PostgreSQL interpreter .................. SKIPPED
    [INFO] Zeppelin: JDBC interpreter ........................ SKIPPED
    [INFO] Zeppelin: File System Interpreters ................ SKIPPED
    [INFO] Zeppelin: Flink ................................... SKIPPED
    [INFO] Zeppelin: Apache Ignite interpreter ............... SKIPPED
    [INFO] Zeppelin: Kylin interpreter ....................... SKIPPED
    [INFO] Zeppelin: Python interpreter ...................... SKIPPED
    [INFO] Zeppelin: Lens interpreter ........................ SKIPPED
    [INFO] Zeppelin: Apache Cassandra interpreter ............ SKIPPED
    [INFO] Zeppelin: Elasticsearch interpreter ............... SKIPPED
    [INFO] Zeppelin: BigQuery interpreter .................... SKIPPED
    [INFO] Zeppelin: Alluxio interpreter ..................... SKIPPED
    [INFO] Zeppelin: web Application ......................... SKIPPED
    [INFO] Zeppelin: Server .................................. SKIPPED
    [INFO] Zeppelin: Packaging distribution .................. SKIPPED
    [INFO] 
------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 07:21 min
    [INFO] Finished at: 2016-08-27T12:30:32+01:00
    [INFO] Final Memory: 63M/903M
    [INFO] 
------------------------------------------------------------------------
    [ERROR] Failed to execute goal on project zeppelin-spark_2.10: Could not 
resolve dependencies for project 
org.apache.zeppelin:zeppelin-spark_2.10:jar:0.7.0-SNAPSHOT: Could not find
     artifact org.apache.zeppelin:zeppelin-display_2.11:jar:0.7.0-SNAPSHOT in 
apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR]
    [ERROR] For more information about the errors and possible solutions, 
please read the following articles:
    [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
    [ERROR]
    [ERROR] After correcting the problems, you can resume the build with the 
command
    [ERROR]   mvn <goals> -rf :zeppelin-spark_2.10
    ```
    and the PR fixes that.
    I cannot currently use the bash script referenced (which just sed-s Scala 
versions in POM files), as currently I am using Windows, but hopefully after 
applying this fix it won't be necessary. I was also looking at the previous 
changes made by doing https://issues.apache.org/jira/browse/ZEPPELIN-1179 and 
it seems the fix is aligned with that approach. What do you think?


---
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