GitHub user pwendell opened a pull request:

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

    [SPARK-3996]: Shade Jetty in Spark deliverables

    (v2 of this patch with a fix that was only relevant for the maven build).
    
    This patch piggy-back's on @vanzin's work to simplify the Guava shading,
    and adds Jetty as a shaded library in Spark. Other than adding Jetty,
    it consilidates the <artifactSet>'s into the root pom. I found it was
    a bit easier to follow that way, since you don't need to look into
    child pom's to find out specific artifact sets included in shading.

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

    $ git pull https://github.com/pwendell/spark jetty

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

    https://github.com/apache/spark/pull/4285.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 #4285
    
----
commit 6df25ca7577211baacf92dbe9466c7ed067afd08
Author: Patrick Wendell <[email protected]>
Date:   2015-01-28T19:37:53Z

    [WIP] [SPARK-3996]: Shade Jetty in Spark deliverables
    
    This patch piggy-back's on @vanzin's work to simplify the Guava shading,
    and adds Jetty as a shaded library in Spark. Other than adding Jetty,
    it consilidates the <artifactSet>'s into the root pom. I found it was
    a bit easier to follow that way, since you don't need to look into
    child pom's to find out specific artifact sets included in shading.

commit 961452d67f3e91ca5f60b0aaf80c59f30d8755ee
Author: Patrick Wendell <[email protected]>
Date:   2015-01-28T21:02:03Z

    Responding to feedback from Marcello

commit 19f07101d47a3ac5ad1a78cb584a515c28271033
Author: Patrick Wendell <[email protected]>
Date:   2015-01-29T01:17:48Z

    More code review feedback

commit d3e7f4e2f6ec070ed4717f955352000fed5c5cb4
Author: Patrick Wendell <[email protected]>
Date:   2015-01-30T02:26:18Z

    Fix for shaded deps causing compile errors

----


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