Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/5504#issuecomment-93087355
The latest change should fix the tests. I realize that now there's some
duplication, and that because I had to restore the Java code to look for the
assembly (see comment in patch), we don't necessarily need to expose it in an
env variable. But being able to control the assembly's location from the shell
scripts was the whole point of #5085, so I guess if we want to support that use
case, the env variable is still needed.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
