GitHub user andrewor14 opened a pull request:

    https://github.com/apache/spark/pull/6511

    [HOT FIX #6441] Fix maven build failures

    Note that this patch reverts the changes in flume-sink because
    this module does not currently depend on Spark core, but the
    tests require it. There is not an easy way to make this work
    because mvn test dependencies are not transitive (MNG-1378).
    
    For now, we will leave the one test suite in flume-sink out
    until we figure out a better solution. This patch is mainly
    intended to unbreak the maven build.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/andrewor14/spark fix-build-mvn

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/6511.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 #6511
    
----
commit 3d5364307e21a1ca2c51fd76fd5466811b0177d0
Author: Andrew Or <[email protected]>
Date:   2015-05-30T00:13:02Z

    [HOT FIX #6441] Fix maven build failures
    
    Note that this patch reverts the changes in flume-sink because
    this module does not currently depend on Spark core, but the
    tests require it. There is not an easy way to make this work
    because mvn test dependencies are not transitive (MNG-1378).
    
    For now, we will leave the one test suite in flume-sink out
    until we figure out a better solution. This patch is mainly
    intended to unbreak the maven build.

----


---
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]

Reply via email to