Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157549041
> For context, my application is pulling in the spark-* artifacts as maven
dependencies
Yeah, that's a different use case, which isn't really covered by my
suggestions. For that case, a different approach might be needed.
Instead of shading, a small pom file could be created to create a
spark-specific version of the old jersey artifacts without the offending files
in META-INF. That way, when you pull jersey transitively via spark-core, you'd
be getting this sanitized jar instead of the original one.
Another approach could be to upgrade the version of jersey used by Spark. I
am not particularly a fan of upgrading dependencies, but it's unlikely people
depend on that dependency currently.
---
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]
