Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3130#issuecomment-70231376
Hey All,
I don't see where spark-submit fits into the issue of having a conflicting
jetty library? If you have an application that requires a conflicting version
of jetty, it doesn't matter one way or the other whether you use spark-submit.
There are certainly applications that do not user spark-submit, and I don't
think we have any issue with that. Databricks Cloud is like this, it embeds
Spark. I think we'll always support that, it will just be more work for those
applications to deal with setting up classpaths, etc in the proper way.
The issue here is just a genuine dependency conflict between a user
application and Spark. We don't have a general purpose way of solving those.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
