[
https://issues.apache.org/jira/browse/SPARK-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173289#comment-14173289
]
Patrick Wendell commented on SPARK-3951:
----------------------------------------
I think the best solution here is actually to mark spark as "provided" in these
external library poms. That way users can link against them and build their own
assemblies that won't include Spark itself. This is consistent with the way
that users in general build Spark applications.
> Make the external-* jars fat jars
> ---------------------------------
>
> Key: SPARK-3951
> URL: https://issues.apache.org/jira/browse/SPARK-3951
> Project: Spark
> Issue Type: Bug
> Reporter: Hari Shreedharan
>
> I am not sure this is the right solution to the issue of having to pull in
> the external jars and all of the dependencies and transitive dependencies,
> but building them as fat jars will definitely solve this, though not in a not
> so elegant way.
> If we build the fat jar, the user can simply deploy this jar and not worry
> about all of the dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
