You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/06/13 00:44:01 UTC

[jira] [Resolved] (SPARK-1843) Provide a simpler alternative to assemble-deps

     [ https://issues.apache.org/jira/browse/SPARK-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell resolved SPARK-1843.
------------------------------------

    Resolution: Fixed

Issue resolved by pull request 877
[https://github.com/apache/spark/pull/877]

> Provide a simpler alternative to assemble-deps
> ----------------------------------------------
>
>                 Key: SPARK-1843
>                 URL: https://issues.apache.org/jira/browse/SPARK-1843
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Patrick Wendell
>            Assignee: Patrick Wendell
>             Fix For: 1.1.0
>
>
> Right now we have the assemble-deps tool for speeding up local development.
> I was thinking about a simpler solution to this problem where, instead of creating a fancy assembly jar, we just add an environment variable: USE_COMPILED_SPARK and, if that variable is present, we simply add the Spark classes on the classpath before the assembly jar. Since the compiled classes are on the classpath first, they will take precedence.
> This would allow us to remove the entire assemble-deps build and associated logic in the bash scripts. We'd need to make sure it's propagated correctly during tests (like SPARK_TESTING) but other than that I think it should work.



--
This message was sent by Atlassian JIRA
(v6.2#6252)