Github user krystiannowak commented on the issue:
https://github.com/apache/zeppelin/pull/1368
@lresende You are totally right - I got a bit mislead by this one
https://github.com/apache/zeppelin/commit/6bb4b5ba8e7ecd6274dd437c6ec5c4a9b178e4d1#diff-d3b6c1f6610ca8471663da11e6225408L78
Github user krystiannowak commented on the issue:
https://github.com/apache/zeppelin/pull/1368
@Leemoonsoo @lresende By doing this patch this way I have followed this
commit
https://github.com/apache/zeppelin/commit/6bb4b5ba8e7ecd6274dd437c6ec5c4a9b178e4d1#diff
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
Github user krystiannowak commented on the issue:
https://github.com/apache/zeppelin/pull/1368
Please try to build the whole project with 2.11 profile turned on. And
possibly clean your local Zeppelin artifacts.
Cheers,
Krystian
27.08.2016 04:43 "Lu
GitHub user krystiannowak opened a pull request:
https://github.com/apache/zeppelin/pull/1368
zeppelin-display dependency version built only for Scala binary version 2.11
### What is this PR for?
Makes the project build again when selecting Scala version 2.11
As per the
Github user krystiannowak commented on the pull request:
https://github.com/apache/zeppelin/commit/0c5a03e6be20a13eee60e84b75cdf2a9dd64d3f4#commitcomment-18792505
It seems it needs to be changed explicitly to _zeppelin-display_2.10_ due
to https://issues.apache.org/jira/browse