GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/877
SPARK-1843: Replace assemble-deps with env variable.
(This change is actually small, I moved some logic into
compute-classpath that was previously in spark-class).
Assemble deps has existed for a while to allow developers to
run local code with new changes quickly. When I'm developing I
typically use a simpler approach which just prepends the Spark
classes to the classpath before the assembly jar. This is well
defined in the JVM and the Spark classes take predece over those
in the assembly.
This approach is portable across both builds which is the main reason I'd
like to switch to it. It's also a bit easier to toggle on and off quickly.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pwendell/spark assemble-deps
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/877.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #877
----
commit f0584a511e5999a3bf84335a2f9a481600822f9b
Author: Patrick Wendell <[email protected]>
Date: 2014-05-26T01:49:51Z
SPARK-1843: Replace assemble-deps with env variable.
(This change is actually small, I moved some logic into
compute-classpath that was previously in spark-class).
Assemble deps has existed for a while to allow developers to
run local code with new changes quickly. When I'm developing I
typically use a simpler approach which just prepends the Spark
classes to the classpath before the assembly jar. This is well
defined in the JVM and the Spark classes take predece over those
in the assembly.
This approach is portable across both builds which is the main reason I'd
like to switch to it. It's also faster than creating a new assembly.
----
---
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.
---
