Github user echarles commented on the issue:
https://github.com/apache/zeppelin/pull/2637
@matyix sure, we can to address the dep in separate PR, especially if it is
beneficial for all deploy modes. The downside of it is that we will have
everybody happy with any change on deps management (if you search the mailing
list, you will a lot of questions and discussions around this).
An additional parameter is the definition of "local" dependencies that
don't come from any maven repo on the Internet. I regularly have to define
local jars on the local disk file system (or even resources files that are not
jar) and with the current `yarn-client` behavior of Zeppelin (probably not for
`yarn-cluster`, I didn't test), those jars/resources are available on the
classpath (of the driver and executor).
If we could inject this now while this branch is being discussed, that
would be really a good thing.
---
