GitHub user zjffdu reopened a pull request:
https://github.com/apache/zeppelin/pull/1880
ZEPPELIN-1918. Fix build with Spark 2.1.0
### What is this PR for?
It's my misunderstanding of `SPARK_VER` in travis. It is only used for
downloading spark distribution. We need to specify spark profile explicitly for
building with specific version of spark. This PR add new profile for spark 2.1
and fix the build issue with spark 2.1.0 because `SecurityManager` changes its
constructor signature in spark 2.1
### What type of PR is it?
[Bug Fix ]
### Todos
* [ ] - Task
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1918
### How should this be tested?
Build with spark 2.1.0 and tested it manually as below screenshot.
### 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/zjffdu/zeppelin ZEPPELIN-1918
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1880.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 #1880
----
commit def502fb708b89e7dbae6321269c2e9a8ef09e4a
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-01-10T07:09:49Z
ZEPPELIN-1918. Fix build with Spark 2.1.0
commit 5efdb11592733cb65a1d9a424e6416349619e341
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-01-10T09:05:35Z
fix unit test and address comments
commit 34772e0bafe517ca5df8eb05ed3eb201e3ecf6ba
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-01-11T02:34:13Z
update build doc for spark 2.1
commit 8f87459bea0949440b5176dbb63fd36952a24207
Author: Jeff Zhang <zjf...@apache.org>
Date: 2017-01-11T02:56:53Z
update release script
----
---
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.
---
