Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.incubator.apache.org
From: dhalperi <git@git.apache.org>
To: commits@beam.incubator.apache.org
Reply-To: commits@beam.incubator.apache.org
Message-ID: <git-pr-431-incubator-beam@git.apache.org>
Subject: [GitHub] incubator-beam pull request #431: Fix pom shading of Guava
Content-Type: text/plain
Date: Wed,  8 Jun 2016 06:28:01 +0000 (UTC)
archived-at: Wed, 08 Jun 2016 06:28:08 -0000

GitHub user dhalperi opened a pull request:

    https://github.com/apache/incubator-beam/pull/431

    Fix pom shading of Guava

    There are two packages: com.google.common and com.google.thirdparty.
    Both need to be repackaged/relocated, but we only had com.google.common
    in a few places.

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

    $ git pull https://github.com/dhalperi/incubator-beam shade-direct-runner

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

    https://github.com/apache/incubator-beam/pull/431.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 #431
    
----
commit aae39c3c980885576ad3b24d30e1705575619714
Author: Dan Halperin <dhalperi@google.com>
Date:   2016-06-08T06:26:46Z

    Fix pom shading of Guava
    
    There are two packages: com.google.common and com.google.thirdparty.
    Both need to be repackaged/relocated, but we only had com.google.common
    in a few places.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---