GitHub user liuxunorg opened a pull request:
https://github.com/apache/zeppelin/pull/3169
[ZEPPELIN-3689] Shade all dependencies of zeppelin-interpreter
### What is this PR for?
The custom interpreter may add other dependencies which conflict with
zeppelin-interpreter's dependency, so it is better to shade
zeppelin-interpreter's dependencies.
### What type of PR is it?
[Improve]
### Todos
* [x] Add new module interpreter-api to shade all dependencies of
zeppelin-interpreter
* [x] Add maven-shade-plugin to interpreter-api/pom.xml
* [x] Add maven-surefire-plugin to interpreter-api/pom.xml
* [x] Filter META-INF/*.SF, META-INF/*.DSA, META-INF/*.RSA
* [x] Zeppelin-interpreter dependency interpreter-api module
* [x] Exclude the interpreter-api module in the interpreter-parent/pom file
to avoid dependency package conflicts
* [x] Exclude the interpreter-api module in the zeppelin-display/pom file
to avoid dependency package conflicts
* [x] Exclude the interpreter-api module in the zeppelin-zengine/pom file
to avoid dependency package conflicts
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-3689
### How should this be tested?
[CI pass](https://travis-ci.org/liuxunorg/zeppelin/builds/424738996)
### 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/liuxunorg/zeppelin ZEPPELIN-3689
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/3169.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 #3169
----
commit beec1a36bbc0a5d3a6e8ab2ae3b46304539d184c
Author: liuxunorg <33611720@...>
Date: 2018-09-05T11:06:37Z
[ZEPPELIN-3689] Shade all dependencies of zeppelin-interpreter
### What is this PR for?
The custom interpreter may add other dependencies which conflict with
zeppelin-interpreter's dependency, so it is better to shade
zeppelin-interpreter's dependencies.
### What type of PR is it?
[Improve]
### Todos
* [x] Added new module interpreter-api to shade all dependencies of
zeppelin-interpreter
* [x] Add maven-shade-plugin to interpreter-api/pom.xml
* [x] Add maven-surefire-plugin to interpreter-api/pom.xml
* [x] filter META-INF/*.SF, META-INF/*.DSA, META-INF/*.RSA
* [x] dependency the interpreter-api module in the
zeppelin-interpreter/pom file
* [x] Exclude the interpreter-api module in the interpreter-parent/pom file
to avoid dependency package conflicts
* [x] Exclude the interpreter-api module in the zeppelin-display/pom file
to avoid dependency package conflicts
* [x] Exclude the interpreter-api module in the zeppelin-zengine/pom file
to avoid dependency package conflicts
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-3689
### How should this be tested?
CI pass
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
----
---
