Github user elbamos commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/463#issuecomment-162332053
Guys - I don't want to be the downer here, but:
* This PR changes what looks like hundreds of lines of the dependency
structure in the build files.
* @tromika - the error you're seeing is what happens when Spark can't start
because of a dependency conflict.
* The PR is going to break literally everything that interfaces with the
spark or spark-dependency modules.
That's what happened when similar changes were made to support 1.5.
* If so much of the dependency structure has to be redone every time
there's a spark release, doesn't that tell us that we need to look at the
architecture of the build cycle?
Why do we need all of these dependencies at all? Aren't they just there to
support launching Spark from under the Zeppelin directory structure -- which is
a "feature" that is being taken out?
I believe there's a pending PR to do just that.
I think we should be looking to see how these dependencies *out* rather
than redoing them for each new Spark release.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
