GitHub user dhalperi opened a pull request:

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

    checkstyle: prohibit API client repackaged Guava

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    Apparently the IllegalImport check only blocks packages,
    so we had to move to Regexp to get individual classes.
    
    As a bonus, this enforcement let us remove two bogus dependencies.
    Smaller JARs for the win!

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

    $ git pull https://github.com/dhalperi/incubator-beam fix-checkstyle

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

    https://github.com/apache/incubator-beam/pull/872.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 #872
    
----
commit 9cb68d5ef5d072172bfea63ef2314f83feae2025
Author: Dan Halperin <dhalp...@google.com>
Date:   2016-08-24T01:54:23Z

    checkstyle: prohibit API client repackaged Guava
    
    Apparently the IllegalImport check only blocks packages,
    so we had to move to Regexp to get individual classes.
    
    As a bonus, this enforcement let us remove two bogus dependencies.
    Smaller JARs for the win!

----


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

Reply via email to